Re: [lwip-users] init network interfaces

[Sergio R. Caprile]

* You are confusing lwIP with a Linux/Un*x environment.
** tap/tun is what a port for that environment does, lwIP is just a
TCP/IP stack, not even a library, the library you are using is a compile
of a port for that environment.
*** You have working examples you are supposed to follow, those will
teach you how to initialize interfaces. Beyond that, you should ask for
help in your environment, whether it is Gnu/Linux or BSD or whatever
UN*X flavor you are using.
** You can't bind to an IP address in your machine because lwIP is not
an application or a library for your machine running on top of its
TCP/IP stack; it is an independent TCP/IP stack written for machines
that don't have other TCP/IP stack and so need it. lwIP needs to see a
link-layer interface. The way you are using it is by providing a virtual
interface via a bridge/router. That is a helper to try and debug other
applications. This has been told many times to some other questions of
yours. Do you understand this ?
*** To reach your lwIP-based application you have to connect to the IP
address YOU provide when you setup the stack. Your tun/tap inet addr is
the gateway address YOU provide so the UN*X internal router can reach
your lwIP stack, and they are configured in the file you are using for
the port, either contrib/ports/unix/proj/minimal/main.c or whatever YOU
are using.
**** Your lwIP-based application will have that IP address as a source
address, your networking environment must route that network, in other
words, if your destination is in other machine, it must know how to "go
back" to your lwIP stack
* Before debugging @application layer, you should check connectivity.
Start by trying a simple ping