Date: Sat, 17 Apr 2004 13:05:39 +0200 From: Andre Oppermann <andre@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: current@freebsd.org Subject: Re: RFC: ported NetBSD if_bridge Message-ID: <40810F83.2030107@freebsd.org> In-Reply-To: <Pine.BSF.4.21.0404170008410.66312-100000@InterJet.elischer.org> References: <Pine.BSF.4.21.0404170008410.66312-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > > On Sat, 17 Apr 2004, Andrew Thompson wrote: >>Hi, >>I have ported over the bridging code from NetBSD and am looking for feedback. >>My main question is, 'do people want this in the tree?' >> >>The benefits over the current bridge are: >> * ability to manage the bridge table >> * spanning tree support >> * the snazzy brconfig utility >> * clonable pseudo-interface (is that a benefit?) > > Do we need THREE bridging systems? > If you need features you culd probably add them pretty easily to one or > the other of the existing bridging modules.. This if_bridge would replace the current bridge(4) code. It doesn't make sense to replicate that. However to keep ipfw working for bridging it needs to be converted to use the standard pfil hooks. ng_bridge is something else with a different scope of application like bridging over UDP etc. This if_bridge code supports IEEE802 spanning-tree which is spoken by all Ethernet switches. If you have larger networks it is very important to have layer 2 loop avoidance. I'm all for adapting this bridge code to FreeBSD provided that ipfw keeps working for bridging. -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40810F83.2030107>