[lwip-users] Testing the internet app based on lwIP-1.3.0 and Mini-OS

[Bei Guan]

Hi All,

lwIP-1.3.0 had been ported to Mini-OS, which is a para-virtualized operating system running on Xen. I just design some experiment to test simple application and I have some problems.

Experiment 1.
I written a simple server and client using the lwIP API. All are running in the Mini-OS. The server start firstly, and then the client start after 10 seconds. However, the client cannot connect to the sever.  I used tcpdump to listen to virtual net bridge interface virbr0 and get message as following. ( The virbr0's IP is 192.168.122.1 )

address@hidden Download]# tcpdump -i virbr0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on virbr0, link-type EN10MB (Ethernet), capture size 96 bytes
17:21:26.284036 arp who-has 192.168.122.20 tell 192.168.122.20
17:21:29.034378 arp who-has 192.168.122.20 tell 192.168.122.20
17:21:32.034868 arp who-has 192.168.122.20 tell 192.168.122.20
17:21:35.035378 arp who-has 192.168.122.20 tell 192.168.122.20
17:21:38.036055 arp who-has 192.168.122.20 tell 192.168.122.20
17:21:41.036521 arp who-has 192.168.122.20 tell 192.168.122.20
17:21:44.036927 arp who-has 192.168.122.20 tell 192.168.122.20

Why Mini-OS cannot connect to itself?  Does lwIP cannot deal with the case.


Experiment 2.
I just running the client, mentioned in experiment 1, but I set the client to connect to the virbr0 ( which ip is 192.168.122.1 ). The tcpdump caught the following data.

address@hidden Download]# tcpdump -i virbr0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on virbr0, link-type EN10MB (Ethernet), capture size 96 bytes
19:27:49.690633 arp who-has 192.168.122.1 tell 192.168.122.20
19:27:50.191296 arp reply 192.168.122.1 is-at fe:ff:ff:ff:ff:ff (oui Unknown)
19:27:50.191474 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:27:49.690656 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52
19:27:52.441109 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:27:52.441148 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52
19:27:54.698700 arp who-has 192.168.122.20 tell 192.168.122.1
19:27:54.698746 arp reply 192.168.122.20 is-at 00:16:3e:60:bb:a1 (oui Unknown)
19:27:55.441726 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:27:55.441756 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52
19:27:58.442208 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:27:58.442241 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52
19:28:01.442863 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:28:01.442901 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52
19:28:04.443371 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:28:04.443405 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52
19:28:07.444012 IP 192.168.122.20.patrolview > 192.168.122.1.10: S 6509:6509(0) win 2048 <mss 1500>
19:28:07.444050 IP 192.168.122.1 > 192.168.122.20: ICMP host 192.168.122.1 unreachable - admin prohibited, length 52

So, my question is what the "patrolview" mean?  I also got other like "drmsfsd", "dpcp", "igo-incognito". What are they mean?
Why the ICMP packets can not reach to host 192.168.122.1?


My Mini-OS net bridge interface information is like these:
address@hidden mini-os]# brctl show
bridge name     bridge id               STP enabled     interfaces
eth0            8000.0024e839fa54       no              peth0
virbr0          8000.feffffffffff             no              vif15.0


Any advice is appreciated.
Best Wishes. 

Bei Guan