[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] [Fwd: Issue with bridge networking]
Hi everyone,
I have some trouble with the network on a domu on a new host : I've made
a bridge and configured it but when I start the domu, I can't ping any
network... seems like the bridge is not working :'(
I've created the bridge directly in /etc/network/interface and I'm using
Xen 3.0.3 on a debian etch, bellow are the xen packages installed on dom0 :
#dpkg -l|grep xen
ii libc6-xen
2.3.6.ds1-13etch8 GNU C Library: Shared libraries
[Xen version
ii linux-headers-2.6.18-6-xen
2.6.18.dfsg.1-23etch1 Common header files for Linux 2.6.18
ii linux-headers-2.6.18-6-xen-686
2.6.18.dfsg.1-23etch1 Header files for Linux 2.6.18 on i686
ii linux-image-2.6.18-6-xen-686
2.6.18.dfsg.1-23etch1 Linux 2.6.18 image on i686
ii linux-modules-2.6.18-6-xen-686
2.6.18.dfsg.1-23etch1 Linux 2.6.18 modules on i686
ii xen-hypervisor-3.0.3-1-i386-pae
3.0.3-0-4 The Xen Hypervisor on i386 with pae
ii xen-linux-system-2.6.18-6-xen-686
2.6.18.dfsg.1-23etch1 XEN system with Linux 2.6.18 image
on i686
ii xen-utils-3.0.3-1
3.0.3-0-4 XEN administrative tools
ii xen-utils-common
3.0.3-0-2 XEN administrative tools - common files
Bellow are all the information I could think of to find the
origin of the issue, let me know if you need anything else :
xen domU config file :
_______________________________________________________
# kernel to use
kernel = "/boot/vmlinuz-2.6.18-6-xen-686"
# kernel ramdisk
ramdisk = "/boot/initrd.img-2.6.18-6-xen-686"
# memory in mb
memory = 128
# CPUs
vcpus = 1
# domain name
name = "artemis"
# root device
root = "/dev/hda1 ro"
# disk mappin
disk = [ 'phy:/dev/rootvg/Artemis,hda1,w' ]
# network bridge
vif = [ 'mac=BB:BB:BB:BB:01:01, bridge=br-pub' ]
_______________________________________________________
dom0 /etc/network/interfaces :
_______________________________________________________
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address xxx.yyy.99.4
netmask 255.255.255.0
network xxx.yyy.99.0
broadcast xxx.yyy.99.255
allow-hotplug eth1
iface eth1 inet static
address xxx.yyy.140.6
netmask 255.255.255.240
network xxx.yyy.140.0
gateway xxx.yyy.140.1
broadcast xxx.yyy.140.15
auto br-pub
iface br-pub inet static
address 0.0.0.0
netmask 0.0.0.0
network 0.0.0.0
bridge_ports eth2
auto br-dmz
iface br-dmz inet static
address 0.0.0.0
netmask 0.0.0.0
network 0.0.0.0
bridge_ports eth3
_______________________________________________________
domU /etc/network/interfaces :
_______________________________________________________
# for xen domain
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address xxx.yyy.140.7
netmask 255.255.255.240
network xxx.yyy.140.0
gateway xxx.yyy.140.1
broadcast xxx.yyy.140.15
_______________________________________________________
brctl show result (when domU is started) :
_______________________________________________________
xxxx:/var/log/xen# brctl show
bridge name bridge id STP enabled interfaces
br-dmz 8000.001b21196811 no eth3
br-pub 8000.001b21196810 no eth2
vif1.0
_______________________________________________________
iptable (when domU is started) :
_______________________________________________________
# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT 0 -- anywhere anywhere PHYSDEV match --physdev-in vif1.0
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Any help is welcome.
Regards,
Jeremie
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
