Date: Wed, 28 Sep 2005 03:29:33 -0700 From: Luigi Rizzo <rizzo@icir.org> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: Peter Jeremy <PeterJeremy@optushome.com.au>, freebsd-arch@freebsd.org, Max Laier <max@love2party.net> Subject: Re: Bridges Message-ID: <20050928032933.G16027@xorpc.icir.org> In-Reply-To: <20050928102153.GA86457@comp.chem.msu.su>; from yar@comp.chem.msu.su on Wed, Sep 28, 2005 at 02:21:53PM %2B0400 References: <200509241525.16173.max@love2party.net> <20050924192237.GP40237@cirb503493.alcatel.com.au> <20050928102153.GA86457@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 28, 2005 at 02:21:53PM +0400, Yar Tikhiy wrote: > On Sun, Sep 25, 2005 at 05:22:38AM +1000, Peter Jeremy wrote: > > > > 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. > > Couldn't you bridge across the parent, or trunk, physical interfaces > carrying tagged VLAN traffic then? (Of course, hardware support for > VLAN should be turned off on them in that case.) yes in fact i was wondering what's wrong with that because we have been using bridge.c like this for ages now... cheers luigi > -- > Yar > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050928032933.G16027>