lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] [lwip] Problems with 0.5.1 release


From: Rajaraman Krishnan
Subject: [lwip-users] [lwip] Problems with 0.5.1 release
Date: Thu, 09 Jan 2003 00:04:24 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_015F_01C1B6FE.583521B0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I tried running LwIP 0.5.1. I am having some problems. First the build under
proj/unixsim failed on tapif.c. The error was as below,

gcc -g -Wall -DIPv4 -DLWIP_DEBUG  -I../../src/include -I../../src/arch/unix/
include -I../../src/include/ipv4 -Iapps -I. -c
../../src/arch/unix/netif/tapif.c
../../src/arch/unix/netif/tapif.c: In function `low_level_init':
../../src/arch/unix/netif/tapif.c:116: `IFF_TAP' undeclared (first use in
this function)
../../src/arch/unix/netif/tapif.c:116: (Each undeclared identifier is
reported only once
../../src/arch/unix/netif/tapif.c:116: for each function it appears in.)
../../src/arch/unix/netif/tapif.c:116: `IFF_NO_PI' undeclared (first use in
this function)
../../src/arch/unix/netif/tapif.c:117: `TUNSETIFF' undeclared (first use in
this function)
../../src/arch/unix/netif/tapif.c: In function `tapif_init':
../../src/arch/unix/netif/tapif.c:420: warning: assignment from incompatible
pointer type
make: *** [tapif.o] Error 1

To get around this I copied the tapif.c from 0.5.0 version and after that
simhost built fine. Then I executed simhost (after modprobe tun).

I tried pinging the simhost. I saw several "Pong!" messages on the simhost
and
the output from tcpdump also looks like simhost did respond to the pings.
But
the ping command on Linux says no packets were received. I have attached the
output from tcpdump (tcpdump.ping).

The I tries to telnet to the simhost. Once again I saw the message "TCP
connection request 1031 -> 23."  on the simhost and once again from tcpdump
it
looks like the simhost did respond. But once again the telnet just hung on
"Trying 192.168.0.2...". I have attached the output from telnet
(tcpdump.telnet).

Let me know what is going on.

Thanks,

Rajaram


------=_NextPart_000_015F_01C1B6FE.583521B0
Content-Type: application/octet-stream;
        name="tcpdum.ping"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
        filename="tcpdum.ping"

address@hidden rajaram]# tcpdump -l -n -i tap0
Kernel filter, protocol ALL, datagram packet socket
tcpdump: listening on tap0
15:28:25.606873 > arp who-has 192.168.0.2 tell 192.168.0.1 =
(0:ff:21:f2:ad:1)
15:28:25.606925 < arp reply 192.168.0.2 is-at 1:12:23:0:0:0 =
(0:ff:21:f2:ad:1)
15:28:25.606933 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:25.607038 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:26.600992 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:26.601148 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:27.600960 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:27.601054 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:28.600999 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:28.601092 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:29.600955 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:29.601050 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:30.600948 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:30.601036 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:31.600955 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:31.601052 P 192.168.0.2 > 192.168.0.1: icmp: echo reply
15:28:32.600923 > arp who-has 192.168.0.2 tell 192.168.0.1 =
(0:ff:21:f2:ad:1)
15:28:32.600954 < arp reply 192.168.0.2 is-at 1:12:23:0:0:0 =
(0:ff:21:f2:ad:1)
15:28:32.601003 > 192.168.0.1 > 192.168.0.2: icmp: echo request
15:28:32.601072 P 192.168.0.2 > 192.168.0.1: icmp: echo reply


------=_NextPart_000_015F_01C1B6FE.583521B0
Content-Type: application/octet-stream;
        name="tcpdum.telnet"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
        filename="tcpdum.telnet"

address@hidden rajaram]# tcpdump -l -n -i tap0
Kernel filter, protocol ALL, datagram packet socket
tcpdump: listening on tap0
15:29:41.510423 > 192.168.0.1.1031 > 192.168.0.2.telnet: S =
1711843063:1711843063(0) win 32120 <mss 1460,sackOK,timestamp 2236448 =
0,nop,wscale 0> (DF)
15:29:41.510580 P 192.168.0.2.telnet > 192.168.0.1.1031: S 6729:6729(0) =
ack 1711843064 win 1024 <mss 128> (DF)
15:29:44.380943 P 192.168.0.2.telnet > 192.168.0.1.1031: S 6729:6729(0) =
ack 1711843064 win 1024 <mss 128> (DF)
15:29:44.500935 > 192.168.0.1.1031 > 192.168.0.2.telnet: S =
1711843063:1711843063(0) win 32120 <mss 1460,sackOK,timestamp 2236748 =
0,nop,wscale 0> (DF)
15:29:46.500922 > arp who-has 192.168.0.2 tell 192.168.0.1 =
(0:ff:21:f2:ad:1)
15:29:46.500957 < arp reply 192.168.0.2 is-at 1:12:23:0:0:0 =
(0:ff:21:f2:ad:1)
15:29:50.500931 > 192.168.0.1.1031 > 192.168.0.2.telnet: S =
1711843063:1711843063(0) win 32120 <mss 1460,sackOK,timestamp 2237348 =
0,nop,wscale 0> (DF)
15:29:50.740940 P 192.168.0.2.telnet > 192.168.0.1.1031: S 6729:6729(0) =
ack 1711843064 win 1024 <mss 128> (DF)
15:30:03.460967 P 192.168.0.2.telnet > 192.168.0.1.1031: S 6729:6729(0) =
ack 1711843064 win 1024 <mss 128> (DF)

------=_NextPart_000_015F_01C1B6FE.583521B0--

[This message was sent through the lwip discussion list.]




reply via email to

[Prev in Thread] Current Thread [Next in Thread]