Linux Ethernet Bridging - Apr 2007 - [Bridge] tagged vlan + bridge: good with xen bad otherwise

On Tuesday 30 January 2007 14:08, Daniele Palumbo wrote:
> first of all, this is not xen-related, but i found the problem managing
> with xen.
> so, knowledge of xen is only suggested.
find out why:
xen do (not by its choise, it's a "bug"):
eth1 - xenbr1 - veth1 - ifconfig veth1 up
                      \ vconfig add veth1 600 - veth1.600 - xenbr1.600
                      \ vconfig add veth1 14 - veth1.14 - xenbr1.14
> i want two type of bridge:
> xenbr1 (with eth1 and other interfaces added later)
> xenbr1.14 (with eth1.14 and other interfaces added later)
>
> xenbr1 must have all the traffic tagged.
> xenbr1.14 must have untagged traffic for vlan 14.
so now:
how can i manage something like:

eth1 - xenbr1
     \ vconfig add eth1 600 - eth1.600 - xenbr1.600
     \ vconfig add eth1 14 - eth1.14 - xenbr1.14
?

in first (working) scenario, the problem is that ALL traffic goes through 
xenbr1... with one more step against second scenario.

thanks
d.

hi.

first of all, this is not xen-related, but i found the problem managing with 
xen.
so, knowledge of xen is only suggested.

the problem:
i want two type of bridge:
xenbr1 (with eth1 and other interfaces added later)
xenbr1.14 (with eth1.14 and other interfaces added later)

xenbr1 must have all the traffic tagged.
xenbr1.14 must have untagged traffic for vlan 14.

i did the following (with eth1 unconfigured)
brctl addbr xenbr1
brctl addif xenbr1 eth1
ifconfig xenbr1 up
ifconfig eth1 up

and xenbr1 is working.
but, when i do a
vconfig add eth1 14
xenbr1 stop working.

if i build up xenbr1.14, with eth1.14, xenbr1.14 works and xenbr1 no.

i have found this: http://ebtables.sourceforge.net/brnf-faq.html
but also setting bridge-nf-filter-vlan-tagged to 0 doesn't help.

but, if i do a xend start, same parameter as my manual config, both xenbr1 and 
xenbr1.14 is working.

there are two notable difference (better, that i noted) between the setup:
- xen rename the interface eth1 in peth1, than it create bridge xenbr1 with 
peth1 and vif0.1, that is a loopback connected to a new interface called eth1 
(that is virtual, not real). 
to understand xen networking: 
http://wiki.xensource.com/xenwiki/XenNetworking?highlight=%28network%29#head-602e26cd4a03b992f3938fe1bea03fa0fea0ed8b
anyway, /proc seems the same between my and xen config, and ifconfig, 
brctl, ... also seems the same.

- in xenbr1, when i setup vconfig add eth1 14, after a while, seems to send 
eth1 in "disabled" mode (brctl showstp xenbr1)

many thank you in advance!

bye
d.

sorry for double posting, was from non registered address.

On Tuesday 30 January 2007 14:08, Daniele Palumbo wrote:
> first of all, this is not xen-related, but i found the problem managing
> with xen.
> so, knowledge of xen is only suggested.
find out why:
xen do (not by its choise, it's a "bug"):
eth1 - xenbr1 - veth1 - ifconfig veth1 up
                      \ vconfig add veth1 600 - veth1.600 - xenbr1.600
                      \ vconfig add veth1 14 - veth1.14 - xenbr1.14
> i want two type of bridge:
> xenbr1 (with eth1 and other interfaces added later)
> xenbr1.14 (with eth1.14 and other interfaces added later)
>
> xenbr1 must have all the traffic tagged.
> xenbr1.14 must have untagged traffic for vlan 14.
so now:
how can i manage something like:

eth1 - xenbr1
     \ vconfig add eth1 600 - eth1.600 - xenbr1.600
     \ vconfig add eth1 14 - eth1.14 - xenbr1.14
?

in first (working) scenario, the problem is that ALL traffic goes through 
xenbr1... with one more step against second scenario.

thanks
d.