M C
2009-Jan-07 11:32 UTC
[Xen-users] Network bridging problem for Centos 5 Dom-O and Debian Etch Dom-U
Hi,
I''ve been trying to get a Debian Etch Dom-U to run on a Centos 5.2
Dom-O, and it seems that the only thing that''s not working is the
bridged networking. I can''t get *any* traffic to or from the Dom-U
instance. The Centos host uses the vmlinuz-2.6.18-92.1.22.el5xen kernel and
associated initrd, whereas the Debian instance uses Debian''s
vmlinuz-2.6.18-6-xen-amd64 image and associated initrd. In the xend-config.sxp
on the Dom-O I''m using the following settings:
(network-script network-bridge)
(vif-script vif-bridge)
The output from ifconfig on the Dom-O is:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:72:1E:C0:C6
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:255.255.255.192
inet6 addr: fe80::213:72ff:fe1e:c0c6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:378586 errors:0 dropped:0 overruns:0 frame:0
TX packets:274778 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:221114065 (210.8 MiB) TX bytes:40271206 (38.4 MiB)
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:16436 Metric:1
RX packets:1571 errors:0 dropped:0 overruns:0 frame:0
TX packets:1571 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2517679 (2.4 MiB) TX bytes:2517679 (2.4 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:423556 errors:0 dropped:0 overruns:0 frame:0
TX packets:274845 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:225506429 (215.0 MiB) TX bytes:41378320 (39.4 MiB)
Interrupt:17
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:274805 errors:0 dropped:0 overruns:0 frame:0
TX packets:378612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:40275516 (38.4 MiB) TX bytes:221115781 (210.8 MiB)
vif22.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:832 (832.0 b) TX bytes:23556 (23.0 KiB)
virbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:176 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6224 (6.0 KiB) TX bytes:10336 (10.0 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:41411 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2481814 (2.3 MiB) TX bytes:0 (0.0 b)
And the output from brctl is:
# brctl show xen-br0
bridge name bridge id STP enabled interfaces
virbr0 8000.feffffffffff yes vif22.0
xenbr0 8000.feffffffffff no peth0
vif0.0
On the Dom-U, I have:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3E:45:D7:B1
inet addr:172.24.116.59 Bcast:172.24.116.63 Mask:255.255.255.192
inet6 addr: fe80::216:3eff:fe45:d7b1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:539 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28028 (27.3 KiB) TX bytes:1140 (1.1 KiB)
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:16436 Metric:1
RX packets:7 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:736 (736.0 b) TX bytes:736 (736.0 b)
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.24.116.0 * 255.255.255.192 U 0 0 0 eth0
default 172.24.116.62 0.0.0.0 UG 0 0 0 eth0
To my newbie eyes these seem OK, and there seem to be packets being received
from somewhere on the Dom-U. However, again on the Dom-U:
# ping 172.24.116.1
PING 172.24.116.1 (172.24.116.1) 56(84) bytes of data.>From 172.24.116.59 icmp_seq=1 Destination Host Unreachable
>From 172.24.116.59 icmp_seq=2 Destination Host Unreachable
>From 172.24.116.59 icmp_seq=3 Destination Host Unreachable
--- 172.24.116.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3005ms,
pipe 3
This is true for any remote address I try to contact.
Can anyone suggest any obvious fixes or further tests that I can run to try and
correct the situation?
Best regards,
mc
_________________________________________________________________
Choose the perfect PC or mobile phone for you
http://clk.atdmt.com/UKM/go/130777504/direct/01/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
M C
2009-Jan-07 15:50 UTC
RE: [Xen-users] Network bridging problem for Centos 5 Dom-O and Debian Etch Dom-U
In case of it''s of any use to anyone else, I got the problem fixed by
explicitly specifying the following in the .cfg script for this VM instance:
vif = [ ''bridge=xenbr0'' ]
I''m not sure if this is the right way to do it, but at least now Debian
Etch seems to be happily running on Centos 5.2.
mc
From: m_c_001@hotmail.com
To: xen-users@lists.xensource.com
Date: Wed, 7 Jan 2009 11:32:50 +0000
Subject: [Xen-users] Network bridging problem for Centos 5 Dom-O and Debian Etch
Dom-U
Hi,
I''ve been trying to get a Debian Etch Dom-U to run on a Centos 5.2
Dom-O, and it seems that the only thing that''s not working is the
bridged networking. I can''t get *any* traffic to or from the Dom-U
instance. The Centos host uses the vmlinuz-2.6.18-92.1.22.el5xen kernel and
associated initrd, whereas the Debian instance uses Debian''s
vmlinuz-2.6.18-6-xen-amd64 image and associated initrd. In the xend-config.sxp
on the Dom-O I''m using the following settings:
(network-script network-bridge)
(vif-script vif-bridge)
The output from ifconfig on the Dom-O is:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:72:1E:C0:C6
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.xxx Mask:255.255.255.192
inet6 addr: fe80::213:72ff:fe1e:c0c6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:378586 errors:0 dropped:0 overruns:0 frame:0
TX packets:274778 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:221114065 (210.8 MiB) TX bytes:40271206 (38.4 MiB)
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:16436 Metric:1
RX packets:1571 errors:0 dropped:0 overruns:0 frame:0
TX packets:1571 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2517679 (2.4 MiB) TX bytes:2517679 (2.4 MiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:423556 errors:0 dropped:0 overruns:0 frame:0
TX packets:274845 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:225506429 (215.0 MiB) TX bytes:41378320 (39.4 MiB)
Interrupt:17
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:274805 errors:0 dropped:0 overruns:0 frame:0
TX packets:378612 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:40275516 (38.4 MiB) TX bytes:221115781 (210.8 MiB)
vif22.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:453 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:832 (832.0 b) TX bytes:23556 (23.0 KiB)
virbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:176 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6224 (6.0 KiB) TX bytes:10336 (10.0 KiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:41411 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2481814 (2.3 MiB) TX bytes:0 (0.0 b)
And the output from brctl is:
# brctl show xen-br0
bridge name bridge id STP enabled interfaces
virbr0 8000.feffffffffff yes vif22.0
xenbr0 8000.feffffffffff no peth0
vif0.0
On the Dom-U, I have:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:3E:45:D7:B1
inet addr:172.24.116.59 Bcast:172.24.116.63 Mask:255.255.255.192
inet6 addr: fe80::216:3eff:fe45:d7b1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:539 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28028 (27.3 KiB) TX bytes:1140 (1.1 KiB)
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:16436 Metric:1
RX packets:7 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:736 (736.0 b) TX bytes:736 (736.0 b)
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.24.116.0 * 255.255.255.192 U 0 0 0 eth0
default 172.24.116.62 0.0.0.0 UG 0 0 0 eth0
To my newbie eyes these seem OK, and there seem to be packets being received
from somewhere on the Dom-U. However, again on the Dom-U:
# ping 172.24.116.1
PING 172.24.116.1 (172.24.116.1) 56(84) bytes of data.>From 172.24.116.59 icmp_seq=1 Destination Host Unreachable
>From 172.24.116.59 icmp_seq=2 Destination Host Unreachable
>From 172.24.116.59 icmp_seq=3 Destination Host Unreachable
--- 172.24.116.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3005ms,
pipe 3
This is true for any remote address I try to contact.
Can anyone suggest any obvious fixes or further tests that I can run to try and
correct the situation?
Best regards,
mc
Are you a PC? Upload your PC story and show the world Click Here!
_________________________________________________________________
Imagine a life without walls. See the possibilities
http://clk.atdmt.com/UKM/go/122465943/direct/01/
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Jan-08 01:44 UTC
Re: [Xen-users] Network bridging problem for Centos 5 Dom-O and Debian Etch Dom-U
M C wrote:> Hi, > > I''ve been trying to get a Debian Etch Dom-U to run on a Centos 5.2 > Dom-O, and it seems that the only thing that''s not working is the > bridged networking. I can''t get *any* traffic to or from the Dom-U > instance.First, some basics. How did you install your CentOS? Did you accept all default values? Is it your first bridged domU, or do you have another bridged domU working on a similar setup? I had the same problem once, turned out it was dom0 iptables that was causing problems (RHEL/Centos turn it on by default). I suggest try "service iptables stop" first on dom0, and if it were the culprit then you need to adjust iptables rules. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Jan-08 02:01 UTC
Re: [Xen-users] Network bridging problem for Centos 5 Dom-O and Debian Etch Dom-U
M C wrote:> In case of it''s of any use to anyone else, I got the problem fixed by > explicitly specifying the following in the .cfg script for this VM > instance: > > vif = [ ''bridge=xenbr0'' ] >Glad to hear you solved it. Looking at your brctl output, # brctl show xen-br0 bridge name bridge id STP enabled interfaces virbr0 8000.feffffffffff yes vif22.0 xenbr0 8000.feffffffffff no peth0 vif0.0 Seems that your domU is attached to virbr0, which is (if I''m not mistaken) a host-only or NAT network. xenbr0 on the other hand is attached to real eth0, which is what you want.> I''m not sure if this is the right way to do it, but at least now > Debian Etch seems to be happily running on Centos 5.2. >You might want to manually assign MAC address so it stays the same for that domU. Something like vif = [ ''mac=00:16:3E:XX:XX:XX, bridge=xenbr0'' ] MAC starting with 00:16:3E is reserverd for Xen -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users