[Pkg-xen-devel] bridging and peth0

[Andy Smith]

Hi Ralph,

On Sun, Jul 15, 2007 at 12:45:09PM +0200, Ralph Passgang wrote:
> > 2b) And should vif0.0 be added to the bridge?  Various guides I have
> >     seen for Debian and Xen only add eth0.
> 
> vif0.0 passes the traffic to your "eth0" interface, which is not the physical 
> interface, but a virtual one. If you don't add vif0.0 to your bridge, your 
> virtual eth0 interface will not get traffic that comes from the bridge. For 
> the default xen-way you definitly need vif0.0 in your bridge.

Yet:

# ip link
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:30:48:60:37:a4 brd ff:ff:ff:ff:ff:ff
4: xenbr0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether 00:30:48:60:37:a4 brd ff:ff:ff:ff:ff:ff
5: intbr0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
8: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
10: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
11: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
12: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
13: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
14: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
15: v-test1: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
16: vi-test1: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
17: v-test2: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
18: vi-test2: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
# brctl show
bridge name     bridge id               STP enabled     interfaces
intbr0          8000.feffffffffff       no              vi-test1
                                                        vi-test2
xenbr0          8000.0030486037a4       no              eth0
                                                        v-test1
                                                        v-test2

The above is what happens with two bridges (xenbr0 and intbr0)
defined in /etc/network/interfaces, xend set to use network-bridge
and vif-bridge, and two domains each with an interface on each
bridge.

In this situation networking seems to all work fine, dom0 can ping
both interfaces of test1 and test2 and vice versa.  So I still don't
understand, what is the purpose of vif0.0 if things work without it?

Cheers,
Andy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20070717/4b956a7c/attachment.pgp