Re: VLAN-aware bridge : [PATCH] Add vlan id to bridge forward database
Faruk Keskin <faruk <at> eit.uni-kl.de>
2008-06-05 23:47:10 GMT
Hi all, hi Stephen,
seems like you've been discussing this issue fairly enough.
However, when you're saying selected vlan's this only works if you have an
exclusive bridge for each vlan.
Unless, the inter-vlan bridging is possible with the current bridging
implementation (same mac address might also a problem). My understanding
is without a vlan aware fdb you'll need multiple bridges to have vlan
specific separate bridging domains enforced by the network topology.
Having a single bridge is desirable because it will simplify dynamic VLAN
management and ease up dynamic configuration, I would suppose.
Yes, the tag gets stripped off when a non-vlan device is forwarded to,
you're right. However, do I want non-vlan devices to get any vlan specific
data as such ? Again, I must properly configure the topology of the
By topology I mean which devices (ethX, ethY.Z, ..) are attached to the
And yes, the extension I mentioned will be used to do some type of sniffing:
an userspace network management tool should among other stuff control the
VLAN configuration over a webinterface. With multiple bridges, the
sniffing will also need some more attention as the might be added and
removed on runtime.
Anyway, thanks you Stephen for the reply.