lwip users (embeddable IP stack)

headers inner T | 2 May 2009 05:31

_______________________________________________
lwip-users mailing list
lwip-users@...
http://lists.nongnu.org/mailman/listinfo/lwip-users
I'm a little confused as to what the actual input function needs to be for
RAW in 1.3.
The possible choices seem to be:

- ip_input()
- ethernetif_input()
- raw_input()
- ethernet_input()

What is the correct input function to use?

Regards, Chris.

HM2 wrote:
> I'm a little confused as to what the actual input function needs to be for
> RAW in 1.3.
> The possible choices seem to be:
>
> - ip_input()
>   
Input function for packets starting with IP header
> - ethernetif_input()
>   
Private input helper function for the example ethernetif (you couldn't 
even use that since it a) does not compile and b) it is declared static!)
> - raw_input()
>   
Input function for packets starting *after* IP header (raw!)
> - ethernet_input()
>   
Input function for packets starting with ethernet header.

The only new function to 1.3.0 is ethernet_input, which implements the 
ethernet-protocol handling (plus ARP) in the tcpip_thread (which was 
previously done elsewhere).

The correct function to use depends on your interface: if you are using 
ethernet, pass the complete received packet to ethernet_input, if you 
use PPP, pass the packet starting with the IP header to ip_input.

There are some example ports in the contrib module that also show this...

Simon

I think there is some confusion about exactly what you want to do, and
why you want to do it?

Regards,
Timmy Brolin

Bandu wrote:
> Hi All,
>  
> thank you very much for you answer.
>  
> Is that mean in LWIP, we need a small routing table ?
>  
> thanks.
>
> On Thu, Apr 30, 2009 at 3:51 PM, Bernhard Wiegel
> <bernhard.wiegel@...
<mailto:bernhard.wiegel@...>> wrote:
>
>     Hello all,
>
>     0.0.0.0 will not work at all!
>
>     The purpose of the netmask is the separation of the host and the
>     network part of the IP-adress.
>
>     Lets make an example: Netmaske 255.255.255.0, IP 192.168.1.23
>     All leading ones of the netmask  -> adress of the subnet  the
>     machine is located. -> subnet: 192.168.1
>     The host can be identified with the zeros of the netmask. -> the
>     host part is 23
>
>     So the netmask really determines the number of hsts within your
>     subnet.
>     Do you have more than 253 hosts in your netmask that you need
>     something different than 255.255.255.0 ?
>
>     Regards,
>     Bernhard
>
>
>     Eric Haver schrieb:
>
>         "0.0.0.0"....That sounds like something reserved.
>
>         On Thu, Apr 30, 2009 at 8:11 AM, Bandu <m.bandu@...
>         <mailto:m.bandu@...> <mailto:m.bandu@...
>         <mailto:m.bandu@...>>> wrote:
>
>            I think that's a good idea.
>            How about if i use 0.0.0.0 mask?
>            On Thu, Apr 30, 2009 at 12:46 PM, Eric Haver
>         <havereric1@... <mailto:havereric1@...>
>            <mailto:havereric1@...
>         <mailto:havereric1@...>>> wrote:
>
>
>
>                On Thu, Apr 30, 2009 at 7:39 AM, Bandu
>         <m.bandu@... <mailto:m.bandu@...>
>                <mailto:m.bandu@... <mailto:m.bandu@...>>>
>         wrote:
>
>                    Is there anyway that I can achieve that?
>
>                A subnet mask of ff.ff.fe.00 would do that, or am I
>         barking up
>                a different tree?
>
>                *E
>
>
>                _______________________________________________
>                lwip-users mailing list
>                lwip-users@... <mailto:lwip-users@...>
>         <mailto:lwip-users@... <mailto:lwip-users@...>>
>
>                http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>
>
>            --    Bandu
>            m.bandu@... <mailto:m.bandu@...>
>         <mailto:m.bandu@... <mailto:m.bandu@...>>
>
>            _______________________________________________
>            lwip-users mailing list
>            lwip-users@... <mailto:lwip-users@...>
>         <mailto:lwip-users@... <mailto:lwip-users@...>>
>
>            http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>         ------------------------------------------------------------------------
>
>
>
>         _______________________________________________
>         lwip-users mailing list
>         lwip-users@... <mailto:lwip-users@...>
>         http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>
>     -- 
>     Dipl-Ing Bernhard Wiegel
>
>     Universität Ulm - Ulm University
>     Institut für Organisation und Management von Informationssystemen
>     (OMI) - Institute for Information Resource Management
>
>     Albert-Einstein-Allee 43
>     89081 Ulm, Germany Tel: +49 731 - 50 28788
>     Fax: +49 731 - 50 28789
>     E-Mail: bernhard.wiegel@...
>     <mailto:bernhard.wiegel@...>
>
>
>
>
>     _______________________________________________
>     lwip-users mailing list
>     lwip-users@... <mailto:lwip-users@...>
>     http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
>
>
> -- 
> Bandu
> m.bandu@... <mailto:m.bandu@...>
> ------------------------------------------------------------------------
>
> _______________________________________________
> lwip-users mailing list
> lwip-users@...
> http://lists.nongnu.org/mailman/listinfo/lwip-users

_______________________________________________
lwip-users mailing list
lwip-users@...
http://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
lwip-users@...
http://lists.nongnu.org/mailman/listinfo/lwip-users

> While trying to compare the ports (provided in contrib) for unix and 
> win32, i found that the following files were not present in unix port:
> lwippools.h

This file is only needed if mem_malloc uses the memp pools, which is not the case for the unix port. The win32
port can be set to that option, thus it needs the file.

> pktdrv.c
> pktdrv.h
> pktif.c
> pktif.h

The win32 port uses the pcap library (known from wireshark, for example), while the unix port uses some
other mechanism to get on the wire (I think tapif or something). Indeed, pktif.c is ethernetif.c adapted
to the pcap library, while pktdrv.c contains the actual code to interface the pcap library (used by pktif.c).

> test.c

This is the entry file (containing the main() function and some initialization). The unix port has a
similar file (though named differently) which does about the same.

> What all modifications should i make so that i have something similar for 
> unix port or are these defined  under some other name.?

The unix port should already work like it is, you don't need to adapt anything, you only might have configure
something to get it working. Unfortunately, I cannot help you there: I tried the unix port myself one time
and found getting the network interface to work quite hard (compared to the windows port which kind of just
works after installing pcap and configuring the MAC/IP addresses in the header file).

> Also, is there any test.c file available for unix port similar to the one 
> in win32?

As I said above, this is the main entry file which the unix port also has (under a different name).

Simon
--

-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

yes as you have mentioned there is a entry file for the examples provided for
unix port.
contrib/ports/unix/proj/unixsim/simhost.c

but im not sure how to use this application. 
i tried the ping option provided but this is the response i got..
Using <some addr1> to ping
Host at <some addr2> mask <some addr3> gateway <some addr4>
System initialized
TCP/IP initializes
sending ping
Applications started

How can i find out if this is working?
yes im breaking my head to find out where the MAC address is being set cause
im getting a new MAC address each time i run this application...did you find
a solution to get around this problem..?

--

-- 
View this message in context: http://www.nabble.com/lwip-on-linux%28ubuntu-8.04%29-tp23363680p23366704.html
Sent from the lwip-users mailing list archive at Nabble.com.

Hi

You already gave me many valuable hints to my questions. Thanks a lot! Now I
have a new one which hopefully someone can answer:

I asked the technical support from ATMEL if it's possible to obtain a time
stamp for a NTP packet at the time it was received (e.g. in the receive
interrupt routine). The answer was simply that NTP was supported by lwIP by
default. Is this true? I have never read anything about this and think that
it's unlikely that NTP belongs to the standard stack...

Regards, Mathias

The MAC address you're seeing is being created by the kernel tap
interface each time you bring simhost up.  If this is your machine
before you run simhost (use a fixed width font for best results):

 ------------------
 | Linux host     |
 |                |
 |          eth0 [|--------- (Your existing network interface)
 |                |
 |                |
 ------------------

This is what it looks like afterward (logically that is; in reality
the simulated lwip host is actually a process running inside your
linux machine):

 ------------------
 | Linux host     |
 |                |
 |          eth0 [|--------- (Your existing network interface)
 |                |
 |                |        ---------------
 |          tap0 [|--------| (simulated) |
 |                |        |  lwip host  |
 ------------------        |             |
                           ---------------

tap0 has the "gateway" address you specified on the simhost command
line (192.168.0.1 by default), the primary IP address specified is the
address of the simulated lwip host (192.168.0.2 by default).

If you use the "-p xx.xx.xx.xx" option, you're pinging out from within
the lwip host.  So the only thing you can really ping is the tap0
"gateway" address (although due to linux idiosyncrasies, it also lets
you ping local interface addresses like the one attached to eth0).

Several things you can try:
Bring up the simhost program (as root).  (For example, "sudo ./simhost")
Then from another shell window, you can ping the lwip simulation with
"ping 192.168.0.2".
You can also telnet to it with "telnet 192.168.0.2" (note that you do
not get a bash shell, you get a limited shell implemented entirely
within the 'fake' lwip host).
Finally, if you have a web browser, you can connect to
http://192.168.0.2 which connects you to the web server implemented
inside the lwip host.

Jeff

On Mon, May 4, 2009 at 7:52 AM, Deepak Gopalakrishnan
<Deepak.Gopalakrishnan@...> wrote:
>
> yes as you have mentioned there is a entry file for the examples provided for
> unix port.
> contrib/ports/unix/proj/unixsim/simhost.c
>
> but im not sure how to use this application.
> i tried the ping option provided but this is the response i got..
> Using <some addr1> to ping
> Host at <some addr2> mask <some addr3> gateway <some addr4>
> System initialized
> TCP/IP initializes
> sending ping
> Applications started
>
> How can i find out if this is working?
> yes im breaking my head to find out where the MAC address is being set cause
> im getting a new MAC address each time i run this application...did you find
> a solution to get around this problem..?
>
> --
> View this message in context: http://www.nabble.com/lwip-on-linux%28ubuntu-8.04%29-tp23363680p23366704.html
> Sent from the lwip-users mailing list archive at Nabble.com.
>
>
>
> _______________________________________________
> lwip-users mailing list
> lwip-users@...
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>

38	May 2013
60	April 2013
71	March 2013
85	February 2013
111	January 2013
98	December 2012
73	November 2012
48	October 2012
97	September 2012
184	August 2012
137	July 2012
186	June 2012
197	May 2012
54	April 2012
125	March 2012
157	February 2012
123	January 2012
86	December 2011
173	November 2011
130	October 2011
275	September 2011
169	August 2011
149	July 2011
110	June 2011
171	May 2011
184	April 2011
163	March 2011
80	February 2011
49	January 2011
105	December 2010
151	November 2010
173	October 2010
105	September 2010
120	August 2010
102	July 2010
111	June 2010
139	May 2010
152	April 2010
231	March 2010
230	February 2010
175	January 2010
91	December 2009
108	November 2009
213	October 2009
232	September 2009
241	August 2009
271	July 2009
178	June 2009
134	May 2009
171	April 2009
214	March 2009
162	February 2009
119	January 2009
138	December 2008
155	November 2008
159	October 2008
128	September 2008
177	August 2008
107	July 2008
47	June 2008
162	May 2008
126	April 2008
185	March 2008
170	February 2008
234	January 2008
138	December 2007
168	November 2007
147	October 2007
177	September 2007
70	August 2007
126	July 2007
155	June 2007
189	May 2007
133	April 2007
239	March 2007
164	February 2007
55	January 2007
52	December 2006
62	November 2006
167	October 2006
142	September 2006
91	August 2006
82	July 2006
54	June 2006
71	May 2006
95	April 2006
98	March 2006
40	February 2006
60	January 2006
77	December 2005
92	November 2005
49	October 2005
45	September 2005
73	August 2005
48	July 2005
70	June 2005
41	May 2005
37	April 2005
41	March 2005
70	February 2005
86	January 2005
109	December 2004
113	November 2004
105	October 2004
126	September 2004
91	August 2004
125	July 2004
109	June 2004
44	May 2004
1	October 2001
1	January 2000

Re: How to handle the passive FIN when waiting (inner T)

Input function for RAW

Re: Input function for RAW

Re: 2 different network number

lwip on linux(ubuntu 8.04)

lwip on linux(ubuntu 8.04)

Re: lwip on linux(ubuntu 8.04)

Re: lwip on linux(ubuntu 8.04)

NTP on lwIP

Re: lwip on linux(ubuntu 8.04)

Mon	Tue	Wed	Thu	Fri	Sat	Sun

				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31