Denny Schierz
2007-May-04 13:14 UTC
[Xen-users] network-bridge problem (maybe debian etch related)
hi,
i installed xen 3. from Debian Etch etc on a very small installation:
dom0:~# dpkg -l | grep xen | cut -d'' '' -f 3
libc6-xen
linux-image-2.6-xen-686
linux-image-2.6.18-4-xen-686
linux-image-xen-686
linux-modules-2.6.18-4-xen-686
xen-hypervisor-3.0.3-1-i386
xen-hypervisor-3.0.3-1-i386-pae
xen-tools
xen-utils-3.0.3-1
After that, i changed /etc/xen/xend-config.conf from:
(network-script network-dummy)
#(network-script network-bridge)
to:
#(network-script network-dummy)
(network-script network-bridge)
i have one network card (vmware) eth0:
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.3.223
netmask 255.255.255.0
gateway 192.168.3.254
Now i starting the Xen environment and i get the following network
configuration:
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: peth0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
4: vif0.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
5: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:0c:29:fa:91:67 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.223/24 brd 192.168.3.255 scope global eth0
inet6 fe80::20c:29ff:fefa:9167/64 scope link
valid_lft forever preferred_lft forever
6: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
9: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
11: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::200:ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
You can see, the eth0 has the IP 233.
The bridge config looks like:
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0
So, everything looks normal and is, how i expected. But, what does not
work, is the network ... I can''t ping (or anything else) from Dom0 to
the outside. I did not installed DomUs, until i understand, what is the
problem.
If i stop the network-bridge script, the network works well again.
Maybe, this is a Debian Etch problem, but it would be nice, to fix it :-)
So, does anybody know what can be the problem?
cu denny
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Denny Schierz
2007-May-04 13:29 UTC
Re: [Xen-users] network-bridge problem (maybe debian etch related)
hi, TMC schrieb:> do you have iproute2 package installed?yepp, "ip" and several tools are included. cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Guillaume Lenoir
2007-May-04 13:44 UTC
RE: [Xen-users] network-bridge problem (maybe debian etch related)
When/where do you declare your bridge ?
Do you declare it by hand ? because I don''t see it in the interfaces
config.
some link that helped me :
http://grml.org/xen/
I''ve struggled with xen networking quite a bit on debian etch amd64 and
I believe my config is not perfect (critics welcome), but I have a
running windows XP VM on the network.
So here it is :
$ sudo dpkg -l | grep xen
ii linux-image-2.6-xen-amd64 2.6.18+6
Linux kernel 2.6 image on AMD64
ii linux-image-2.6.18-4-xen-amd64 2.6.18.dfsg.1-12etch1
Linux 2.6.18 image on AMD64
ii linux-image-xen-amd64 2.6.18+6
Linux kernel image on AMD64
ii linux-modules-2.6.18-4-xen-amd64 2.6.18.dfsg.1-12etch1
Linux 2.6.18 modules on AMD64
ii xen-docs-3.0 3.0.3-0-2
documentation for XEN, a Virtual Machine Mon
ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2
The Xen Hypervisor on AMD64
ii xen-ioemu-3.0.3-1 3.0.3-0-2
XEN administrative tools
ii xen-linux-system-2.6.18-4-xen-amd64 2.6.18.dfsg.1-12etch1
XEN system with Linux 2.6.18 image on AMD64
ii xen-tools 2.8-2
Tools to manage debian XEN virtual servers
ii xen-utils-3.0.3-1 3.0.3-0-2
XEN administrative tools
ii xen-utils-common 3.0.3-0-2
XEN administrative tools - common files
ii xenman 0.5-2.1
A graphical Xen management tool
$ more /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
auto eth0
allow-hotplug eth0
iface eth0 inet static
# <snip> normal static eth config</snip>
auto xenbr0
iface xenbr0 inet static
pre-up brctl addbr xenbr0
post-down brctl delbr xenbr0
bridge_fd 0
bridge_hello 0
bridge_stp off
$ grep vif /etc/xen/mywindowsxp.hvm
vif = [ ''type=ioemu, mac=00:16:3e:08:df:13, bridge=xenbr0'' ]
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Denny
Schierz
Sent: Friday, 04 May, 2007 3:15 PM
To: ''xen-users@lists.xensource.com''
Subject: [Xen-users] network-bridge problem (maybe debian etch related)
hi,
i installed xen 3. from Debian Etch etc on a very small installation:
dom0:~# dpkg -l | grep xen | cut -d'' '' -f 3 libc6-xen
linux-image-2.6-xen-686
linux-image-2.6.18-4-xen-686
linux-image-xen-686
linux-modules-2.6.18-4-xen-686
xen-hypervisor-3.0.3-1-i386
xen-hypervisor-3.0.3-1-i386-pae
xen-tools
xen-utils-3.0.3-1
After that, i changed /etc/xen/xend-config.conf from:
(network-script network-dummy)
#(network-script network-bridge)
to:
#(network-script network-dummy)
(network-script network-bridge)
i have one network card (vmware) eth0:
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.3.223
netmask 255.255.255.0
gateway 192.168.3.254
Now i starting the Xen environment and i get the following network
configuration:
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: peth0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
3: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
4: vif0.0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::fcff:ffff:feff:ffff/64 scope link
valid_lft forever preferred_lft forever
5: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:0c:29:fa:91:67 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.223/24 brd 192.168.3.255 scope global eth0
inet6 fe80::20c:29ff:fefa:9167/64 scope link
valid_lft forever preferred_lft forever
6: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
9: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
11: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
12: xenbr0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
inet6 fe80::200:ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
You can see, the eth0 has the IP 233.
The bridge config looks like:
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no vif0.0
peth0 So,
everything looks normal and is, how i expected. But, what does not work,
is the network ... I can''t ping (or anything else) from Dom0 to the
outside. I did not installed DomUs, until i understand, what is the
problem.
If i stop the network-bridge script, the network works well again.
Maybe, this is a Debian Etch problem, but it would be nice, to fix it
:-)
So, does anybody know what can be the problem?
cu denny
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Denny Schierz
2007-May-04 15:34 UTC
Re: [Xen-users] network-bridge problem (maybe debian etch related)
hi, Guillaume Lenoir schrieb:> When/where do you declare your bridge ? > Do you declare it by hand ? because I don''t see it in the interfaces > config.that is, what i do not understand. The bridge exists, i posted the "brctl show" output. I red, that: 1. a bridge, called xenbr0, would created 2. the real eth0 brought down 3. the IP from the eth0 are copied to veth0 4. the real eth0 renamed to peth0 5. virtual veth0 ist now eth0 on Dom0 6. peth0 and vif0.0 are connected via xenbr0 bridge 7. the bridge, peth0, eth0 and vif0.0 are brought up so, why i have to declare a xenbr0 in /etc/interfaces? or, in the grml howto, xenintbr?> auto xenbr0 > iface xenbr0 inet static > pre-up brctl addbr xenbr0 > post-down brctl delbr xenbr0 > bridge_fd 0 > bridge_hello 0 > bridge_stp offhowever, this does not work for me. Debian tells me, that are some variables are missing and xenbr0 exists, while Xend (closer, while network-bridge script) is running. cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcin Owsiany
2007-May-04 15:53 UTC
Re: [Xen-users] network-bridge problem (maybe debian etch related)
On Fri, May 04, 2007 at 03:14:57PM +0200, Denny Schierz wrote:> So, does anybody know what can be the problem?Checksum offloading? Or does it only cause problems in domUs? -- Marcin Owsiany <marcin@owsiany.pl> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 "Every program in development at MIT expands until it can read mail." -- Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Denny Schierz
2007-May-04 17:51 UTC
Re: [Xen-users] network-bridge problem (maybe debian etch related)
hi, Marcin Owsiany schrieb:> Checksum offloading? Or does it only cause problems in domUs?there is no DomU running jet. First i want to understand the network. cu denny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Denny Schierz
2007-May-04 20:04 UTC
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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users