Greetings Faruk, I'm not knowledgeable enough to comment on the approach but I am very interested in your progress on the matter. We are currently deploying a solution where being able to link different vlans off a trunk would be a lifesaver. It was always problematic, something to do with the bridge not forwarding some (but not all) arp replies properly. Jonathan Faruk Keskin wrote: > Hello everybody, hi Jaime, > > I'm mailing to get more information about whether your patch > [PATCH] Add vlan id to bridge forward database > has been accepted so far. > I couldn't find the patched version yet - could you please tell me where I > can get the latest version of the patch or point out a reference to it ? > > Has the vlan-aware bridge forwarding already been tested ? > > And how about forwarding tagged packets ? > Until now, the bridge always stripped off the tag if present. > > I'm currently thinking about extending the sk_buff data structure to > incorporate the vlan tag - to keep the VLAN information present when > exchanging packets from or to the bridge with the 8021q module and also > when a socket is bind to a interface (extending the sockaddr_ll struct in > that case). > > Do you think thats's a sane approach ? > > Thanks in advance, Faruk > > > > > > _______________________________________________ > Bridge mailing list > Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx > https://lists.linux-foundation.org/mailman/listinfo/bridge > _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
