Date: Tue, 18 May 2004 18:09:19 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Jaye Mathisen <mrcpu@cdsnet.net> Cc: current@freebsd.org Subject: Re: Limitations of -curent Bridinging... Message-ID: <Pine.BSF.4.21.0405181807330.41838-100000@InterJet.elischer.org> In-Reply-To: <20040518224917.GA6273@backmaster.cdsnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 18 May 2004, Jaye Mathisen wrote: > > > > WHat exactly is the issue (besides no loop detection support) > in 5.x? > > I was going to use 5.x as a bridge between my main router > and the rest of my network, mainly for trafshow/iftop type stuff. > > Of course, I want the ability to ipfw on it as well, if I need to, > and possibly traffic shape with dummynet. Possibly snort as well, although > I'm not sure. > > If I can't do that, then will Netgraph work, and give me something that > I can actually filter with? No, the netgraph ipfw node has never been committed. give a node to do what you want it would work, but while it was written it was never documented well enough to add and it never happenned.. > > Or do I need to switch BSD's and go with Open for this project, because > their bridging code has some function that I'm not comprehending (besides STP). > > > Is there anything wrong with this plan? > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0405181807330.41838-100000>