[Xen-users] network-bridge problem (maybe debian etch related)

[Denny Schierz <linuxmail@xxxxxxxx>]

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

Attachment: signature.asc
Description: OpenPGP digital signature

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