Stephan Schwab
2006-Apr-10 03:52 UTC
[Xen-users] ARP requests from domU not answered on network
Hi!
This is getting a bit strange. I have a working Xen setup on Ubuntu.
dom0 is 2.6.12.6-xen0 and domU is 2.6.12.6-xenU. But I have problems
reaching any target outside the Xen host.
The DHCP server is on the network and external to the Xen host. The
IP addresses used are:
dom0: 192.168.1.200
domU: 192.168.1.121 obtained via DHCP
I can ping back and forth between .200 (dom0) and .121 (domU) and can
see the traffic via tcpdump on xenbr0.
When I ping another host on the network I see this on the bridge:
23:38:37.431863 arp who-has 192.168.1.101 tell 192.168.1.121
and in domU:
From 192.168.1.121 icmp_seq=1 Destination Host Unreachable
ifconfig on dom0 shows:
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20628 errors:0 dropped:0 overruns:0 frame:0
TX packets:41155 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1949792 (1.8 MiB) TX bytes:9541427 (9.0 MiB)
Interrupt:18 Base address:0x1400
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:54 errors:0 dropped:0 overruns:0 frame:0
TX packets:3872 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2268 (2.2 KiB) TX bytes:624258 (609.6 KiB)
vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:450 errors:0 dropped:0 overruns:0 frame:0
TX packets:3071 errors:0 dropped:298 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21628 (21.1 KiB) TX bytes:482186 (470.8 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:
255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17726 errors:0 dropped:0 overruns:0 frame:0
TX packets:37781 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1393935 (1.3 MiB) TX bytes:9203473 (8.7 MiB)
ifconfig in domU:
eth0 Link encap:Ethernet HWaddr 00:16:3E:5F:9E:40
inet addr:192.168.1.121 Bcast:192.168.1.255 Mask:
255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3204 errors:0 dropped:0 overruns:0 frame:0
TX packets:412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:493011 (481.4 KiB) TX bytes:20032 (19.5 KiB)
Anyone has any idea where to look for the reason of this behavior?
Stephan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Stephan Schwab
2006-Apr-11 21:42 UTC
Re: [Xen-users] ARP requests from domU not answered on network
This strange problem was caused by running the Xen host inside a VMware virtual machine that could not set its interface to promiscous mode. It was not a problem with Xen. On Apr 9, 2006, at 11:52 PM, Stephan Schwab wrote:> Hi! > > This is getting a bit strange. I have a working Xen setup on > Ubuntu. dom0 is 2.6.12.6-xen0 and domU is 2.6.12.6-xenU. But I have > problems reaching any target outside the Xen host. > > The DHCP server is on the network and external to the Xen host. The > IP addresses used are: > > dom0: 192.168.1.200 > domU: 192.168.1.121 obtained via DHCP > > I can ping back and forth between .200 (dom0) and .121 (domU) and > can see the traffic via tcpdump on xenbr0. > > When I ping another host on the network I see this on the bridge: > > 23:38:37.431863 arp who-has 192.168.1.101 tell 192.168.1.121 > > and in domU: > > From 192.168.1.121 icmp_seq=1 Destination Host Unreachable > > ifconfig on dom0 shows: > > peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:20628 errors:0 dropped:0 overruns:0 frame:0 > TX packets:41155 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1949792 (1.8 MiB) TX bytes:9541427 (9.0 MiB) > Interrupt:18 Base address:0x1400 > > vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:54 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3872 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2268 (2.2 KiB) TX bytes:624258 (609.6 KiB) > > vif3.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:450 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3071 errors:0 dropped:298 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:21628 (21.1 KiB) TX bytes:482186 (470.8 KiB) > > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet addr:192.168.1.200 Bcast:192.168.1.255 Mask: > 255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:17726 errors:0 dropped:0 overruns:0 frame:0 > TX packets:37781 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1393935 (1.3 MiB) TX bytes:9203473 (8.7 MiB) > > ifconfig in domU: > > eth0 Link encap:Ethernet HWaddr 00:16:3E:5F:9E:40 > inet addr:192.168.1.121 Bcast:192.168.1.255 Mask: > 255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3204 errors:0 dropped:0 overruns:0 frame:0 > TX packets:412 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:493011 (481.4 KiB) TX bytes:20032 (19.5 KiB) > > Anyone has any idea where to look for the reason of this behavior? > > Stephan > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users