[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] network-bridge problem (maybe debian etch related)
hi, ok, next try. I made a ping from my wks to the dom0 (which is running in vmware) and listen per tcpdump on my laptop note: anjali 192.168.3.160 is my wks kusanagi 192.168.3.163 is my laptop with vmware and (etch) Xen inside 192.168.3.223 192.168.3.254 is my router with switch ping from anjali to xen dom0 and vice versa i get on kusanagi: 21:42:07.783352 IP anjali > 192.168.3.223: ICMP echo request, id 1571, seq 738, length 64 21:42:08.789098 IP anjali > 192.168.3.223: ICMP echo request, id 1571, seq 739, length 64 21:42:09.792938 IP anjali > 192.168.3.223: ICMP echo request, id 1571, seq 740, length 64 21:42:10.794845 IP anjali > 192.168.3.223: ICMP echo request, id 1571, seq 741, length 64 21:42:11.208736 arp who-has anjali tell 192.168.3.223 21:42:11.208748 arp who-has anjali tell 192.168.3.223 on anjali the same: 21:49:32.831500 arp who-has 192.168.3.223 tell anjali 21:49:33.831497 arp who-has 192.168.3.223 tell anjali 21:49:34.506155 arp who-has anjali tell 192.168.3.223 On Dom0 i get "destination unreachable" with ping with tcpdump on: vif0.0, xenbr0, and eth0 ... arp who-has 192.168.3.160 tell 192.168.3.223 ... arp who-has 192.168.3.160 tell 192.168.3.223 ... arp who-has 192.168.3.160 tell 192.168.3.223 ... arp who-has 192.168.3.160 tell 192.168.3.223 [...] so, it looks like a arp problem: on dom0 arp -a: ? (192.168.3.254) on <uncomplete> on eth0 ? (192.168.3.160) on <uncomplete> on eth0 if i stop the script: /etc/xen/scripts/network-bridge stop, everything works quite normal. any suggestions? cu denny Attachment:
signature.asc _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |