Date: Thu, 28 Sep 2000 09:39:11 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Julian Elischer <julian@elischer.org> Cc: "Boyd R. Faulkner" <faulkner@asgard.hos.net>, "Peter S. Housel" <housel@acm.org>, freebsd-current@FreeBSD.ORG Subject: Re: Network bridge on current. Message-ID: <20000928093910.A24037@dan.emsphone.com> In-Reply-To: <Pine.BSF.4.10.10009280032180.17364-100000@InterJet.elischer.org>; from "Julian Elischer" on Thu Sep 28 00:38:40 GMT 2000 References: <20000928022230.A967@simon.catburg.net> <Pine.BSF.4.10.10009280032180.17364-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Sep 28), Julian Elischer said: > On Thu, 28 Sep 2000, Boyd R. Faulkner wrote: > > On Thu, Sep 28, 2000 at 12:11:54AM -0700, Peter S. Housel wrote: > > > On Thu, 28 Sep 2000, Boyd R. Faulkner wrote: > > > > I am wondering how to do network bridging on current. The > > > > description in the handbook seems to be out of date as the > > > > sysctl IODs are no longer in evidence. Does loading ng_bridge > > > > substitute for building the kernel with OPTIONS BRIDGE? > > > > > > Excuse my ignorance (and curiousity), but wouldn't it be cheaper > > > to just buy a switch? > > > > I intend to use it as a firewall. The switch will live behind it. > > I am not sure about Luigi's bridging code. I know the dummynet stuff > seems to connect with the ipfw code but I don't think that the bridge > code does... (I may be wrong) So I don't know how you plan on > filtering the bridged segments.. ipfw definitely supports filtering bridged packets; there's even a "bridge" keyword to match them explicitly. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000928093910.A24037>