|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [MirageOS-devel] Routing.No_route_to_destination_address running Mirage web server
192.168.1.103 is my Mac
192.168.1.1 is my laptop which is a Xen host
>>Output of `ifconfig` in dom0 may also be useful...?
from 192.168.1.1
ifconfig -a
root@contiki:/home/ubuntu# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4883 (4.8 KB) TX bytes:4883 (4.8 KB)
p2p1 Link encap:Ethernet HWaddr f8:a9:63:4a:2f:65
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2034949 errors:0 dropped:0 overruns:0 frame:0
TX packets:49325 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1306847225 (1.3 GB) TX bytes:21560010 (21.5 MB)
wlan0 Link encap:Ethernet HWaddr 30:3a:64:af:08:b1
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
xenbr0 Link encap:Ethernet HWaddr f8:a9:63:4a:2f:65
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::faa9:63ff:fe4a:2f65/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101804 errors:0 dropped:6 overruns:0 frame:0
TX packets:48823 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:80428756 (80.4 MB) TX bytes:21535927 (21.5 MB)
root@contiki:/home/ubuntu#
>> Would you be able to run tcpdump on dom0 to capture the packets on xenbr0
>> during the problem?
18:04:34.751705 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 00:16:3e:0b:8c:b2 (oui Unknown), length 552
18:04:34.754623 ARP, Request who-has 192.168.1.118 tell 192.168.1.254, length 46
18:04:35.073860 IP 192.168.1.1.56640 > google-public-dns-a.google.com.domain:
32842+ PTR? 255.255.255.255.in-addr.arpa. (46)
18:04:35.095372 IP google-public-dns-a.google.com.domain > 192.168.1.1.56640:
32842 NXDomain 0/1/0 (114)
18:04:35.095933 IP 192.168.1.1.49621 > google-public-dns-a.google.com.domain:
53358+ PTR? 0.0.0.0.in-addr.arpa. (38)
18:04:35.253334 IP google-public-dns-a.google.com.domain > 192.168.1.1.49621:
53358 NXDomain 0/1/0 (106)
18:04:35.253926 IP 192.168.1.1.39641 > google-public-dns-a.google.com.domain:
42061+ PTR? 118.1.168.192.in-addr.arpa. (44)
18:04:35.275753 IP google-public-dns-a.google.com.domain > 192.168.1.1.39641:
42061 NXDomain 0/0/0 (44)
18:04:35.742541 ARP, Request who-has 192.168.1.118 tell 192.168.1.254, length 46
18:04:35.744513 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request
from 00:16:3e:0b:8c:b2 (oui Unknown), length 552
18:04:35.759648 ARP, Reply 192.168.1.118 is-at 00:16:3e:0b:8c:b2 (oui Unknown),
length 28
18:04:35.760446 ARP, Request who-has 192.168.1.254 (Broadcast) tell
192.168.1.118, length 28
18:04:40.081644 ARP, Request who-has 192.168.1.1 tell 192.168.1.254, length 46
18:04:40.081688 ARP, Reply 192.168.1.1 is-at f8:a9:63:4a:2f:65 (oui Unknown),
length 28
18:04:40.202520 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 253
18:04:40.203443 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:04:40.204363 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 327
18:04:40.205246 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 325
18:04:40.206343 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 321
18:04:40.207293 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 301
18:04:40.208165 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 333
18:04:40.209021 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 315
18:04:40.209917 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:04:40.210819 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:10.127384 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 253
18:05:10.128315 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:10.129214 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 327
18:05:10.130115 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 325
18:05:10.131016 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 321
18:05:10.131872 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 301
18:05:10.132744 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 333
18:05:10.133642 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 315
18:05:10.134542 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:10.135443 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:19.093280 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 407
18:05:19.114282 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 416
18:05:19.136352 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 463
18:05:19.157109 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 471
18:05:19.177950 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 473
18:05:19.198741 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 461
18:05:19.219891 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 447
18:05:19.320863 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 407
18:05:19.342378 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 416
18:05:19.365113 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 463
18:05:19.386710 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 471
18:05:19.408173 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 473
18:05:19.430274 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 461
18:05:19.451756 IP 192.168.1.115.52323 > 239.255.255.250.1900: UDP, length 447
18:05:20.094903 IP 192.168.1.1.49362 > google-public-dns-a.google.com.domain:
7308+ PTR? 115.1.168.192.in-addr.arpa. (44)
18:05:20.118259 IP google-public-dns-a.google.com.domain > 192.168.1.1.49362:
7308 NXDomain 0/0/0 (44)
18:05:25.095635 ARP, Request who-has 192.168.1.254 tell 192.168.1.1, length 28
18:05:25.096152 ARP, Reply 192.168.1.254 is-at 00:04:ed:b2:9d:0e (oui Unknown),
length 46
18:05:31.559255 ARP, Request who-has 192.168.1.118 tell 192.168.1.103, length 46
18:05:31.560938 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:32.104190 IP 192.168.1.1.53235 > google-public-dns-a.google.com.domain:
42097+ PTR? 103.1.168.192.in-addr.arpa. (44)
18:05:32.126014 IP google-public-dns-a.google.com.domain > 192.168.1.1.53235:
42097 NXDomain 0/0/0 (44)
18:05:33.061136 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:34.561235 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:36.061430 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:37.108474 ARP, Request who-has 192.168.1.1 tell 192.168.1.254, length 46
18:05:37.108518 ARP, Reply 192.168.1.1 is-at f8:a9:63:4a:2f:65 (oui Unknown),
length 28
18:05:37.568855 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:39.069039 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:40.052202 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 253
18:05:40.053153 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:40.054033 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 327
18:05:40.055161 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 325
18:05:40.056071 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 321
18:05:40.056969 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 301
18:05:40.057873 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 333
18:05:40.058756 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 315
18:05:40.059646 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:40.060571 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:05:40.569169 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:42.069264 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:44.572788 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:46.072930 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:47.573089 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:49.073256 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:50.621140 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:52.121252 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:53.621365 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:55.121496 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:57.576917 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:05:59.077114 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:06:00.577260 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:06:02.077380 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:06:03.598891 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
^C
171 packets captured
171 packets received by filter
0 packets dropped by kernel
root@contiki:/home/ubuntu/mirage-test#
>>Maybe also ping 192.168.1.103 from dom0 afterwards in the same capture?
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.991/1.275/1.458/0.203 ms
andrew-stuarts-macbook-pro:~ andrewstuartsupercoders$ ping 192.168.1.118
PING 192.168.1.118 (192.168.1.118): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
4.725972 ARP, Request who-has 192.168.1.118 tell 192.168.1.103, length 46
18:08:34.727239 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:36.227419 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:37.727567 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:39.227718 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:39.601421 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 253
18:08:39.602367 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:08:39.603252 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 327
18:08:39.604158 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 325
18:08:39.604994 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 321
18:08:39.605881 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 301
18:08:39.606773 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 333
18:08:39.607676 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 315
18:08:39.608575 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:08:39.609460 IP 192.168.1.254.nfs > 239.255.255.250.1900: UDP, length 317
18:08:40.743315 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:42.243504 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:43.743664 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:45.243787 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:46.760310 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
18:08:48.260488 ARP, Request who-has 192.168.1.103 (Broadcast) tell
192.168.1.118, length 28
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |