Re: [Xen-users] Networking issue on DomU

[Ernst Bachmann <e.bachmann@xxxxxxxx>]

Hi,

On Friday 08 July 2005 13:25, Nico wrote:
> Hello lists.
>
> Having a problem getting network to work inside a domU.
>
> I have 2 guests os's (the example ttylinux and a CentOS 3,3 domU).
>
> the 2 domU's can ping each other, the dom0 can ping the outside world, incl
> internet.
> The 2 domU's can not ping the dom0 (or anything else) and the dom0 can not
> ping the domU's.
>
> Config dom0
> Host OS is CentOS 4.0 with xen 2.0.6
>
> [root@vps xen]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:60:08:6D:1E:C6
>           inet addr:10.0.0.211  Bcast:10.0.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:125239 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1677 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:17073332 (16.2 MiB)  TX bytes:132617 (129.5 KiB)
>           Interrupt:10 Base address:0x1480
>
> eth1      Link encap:Ethernet  HWaddr 00:04:76:13:92:DA
>           inet addr:10.0.0.210  Bcast:10.0.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:113302 errors:0 dropped:0 overruns:1 frame:0
>           TX packets:39535 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:22 txqueuelen:1000
>           RX bytes:14854554 (14.1 MiB)  TX bytes:4235423 (4.0 MiB)
>           Interrupt:9 Base address:0x1400
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:42137 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:42137 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:3030632 (2.8 MiB)  TX bytes:3030632 (2.8 MiB)
>
> vif30.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:34 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:90 errors:0 dropped:145 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:2378 (2.3 KiB)  TX bytes:4540 (4.4 KiB)
>
> vif51.0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:20 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:1120 (1.0 KiB)  TX bytes:462 (462.0 b)
>
> xen-br0   Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet addr:10.0.0.212  Bcast:10.255.255.255  Mask:255.0.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:335 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:15764 (15.3 KiB)  TX bytes:756 (756.0 b)

Looks like your bridge isn't setup correctly.
at least one of your real network ifaces (eth0 or eth1) should be running 
without IP Address, be enslaved to xen-br0, and xen-br0 should have the IP it 
had earlier.
the bridge should then use the HW/MAC Addr of that nic.

check "brctl show xen-br0"

If you don't want to bridge your network directly, but route instead, you'd 
have to setup a MAC Addr for that bridge, give it an IP from a different 
subnet, enable routing, and enable IP-Forwarding.

Hope that pointed you in the right direction,
/Ernst

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users