Date: Tue, 4 Oct 2005 12:09:45 -0700 (PDT) From: Doug Ambrisko <ambrisko@ambrisko.com> To: PeterJeremy@optushome.com.au Cc: freebsd-arch@freebsd.org Subject: Re: Bridges Message-ID: <200510041909.j94J9jvd093228@ambrisko.com> In-Reply-To: <20050925002212.GA77857@heff.fud.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 25, 2005 at 05:22:38AM +1000, Peter Jeremy wrote: > On Sat, 2005-Sep-24 15:25:06 +0200, Max Laier wrote: > >for some time now, we have three bridge implementations in the tree: > > - net/bridge.c - the "old" bridge > > - net/if_bridge.c - the "new" bridge from Net/OpenBSD > > - netgraph/ng_bridge.c - the netgraph version [1] > > > >The new code has several advantages over the old version: > > - Spanning Tree Protocol (802.1D) > > - better firewall support (IPv6, stateful filtering, ...) > > - easy ifconfig(8) configuration > > Since I've recently needed it, neither bridge.c nor if_bridge.c allow > you to bridge VLAN trunks (you can bridge individual VLANs but that > becomes unwieldly when you have dozens of VLANs). I have code to do > this in bridge.c. I think I ran into the related problem. The vlan device calls IFQ_HANDOFF directly versus the "normal" output bits so you can't use netgraph etc. I broke up ether_output so that I could call the stuff that ether_output does so it would go through netgraph hooks if configured. Doug A.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510041909.j94J9jvd093228>