Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: unicast-flooding-2.6.20.4.patch Type: text/x-patch Size: 3300 bytes Desc: not available Url : http://lists.linux-foundation.org/pipermail/bridge/attachments/20070416/4585d8f0/unicast-flooding-2.6.20.4-0002.bin
Stephen Hemminger
2007-Apr-18 17:23 UTC
[Bridge] Feature enhancement - Disable unicast flooding
On Mon, 16 Apr 2007 10:29:31 +1200 Dylan Hall <dylan@citylink.co.nz> wrote:> For the project I'm working on I require that the bridging code not > flood unicast frames when the destination mac address is unknown, > similar to Cisco's "switchport block unicast" feature > (http://www.cisco.com/en/US/products/ps6406/products_configuration_guide_chapter09186a00805a761a.html#wp1087814). > > I have produced a small patch (against 2.6.20.4) to control this feature > per bridge (rather than per port like a Cisco). > > Have I gone about implementing this correctly? > > Is this something other people may find useful, and hence worth > incorporating into the mainstream code? > > Is it worth the effort of taking this one step further, and controlling > the behaviour per port rather than per bridge? > > Thanks, > > Dylan > > >Maybe. But this kind of thing is better done with a ebtables module. That way it can be more easily integrated with other security stuff.