Date: Tue, 8 Aug 2000 07:15:46 -0400 From: "Vladimir N. Silyaev" <vsilyaev@mindspring.com> To: Akinori -Aki- MUSHA <knu@idaemons.org> Cc: Robert Watson <rwatson@FreeBSD.ORG>, freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000808071546.C360@jupiter.delta.ny.us> In-Reply-To: <86bsz4co1p.wl@localhost.local.idaemons.org>; from knu@idaemons.org on Tue, Aug 08, 2000 at 02:36:02PM %2B0900 References: <200008032335.TAA01440@jupiter.delta.ny.us> <Pine.NEB.3.96L.1000806190759.90634A-100000@fledge.watson.org> <20000806232339.A3251@jupiter.delta.ny.us> <86bsz4co1p.wl@localhost.local.idaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 08, 2000 at 02:36:02PM +0900, Akinori -Aki- MUSHA wrote: > At a quick glance, "start_bridge" doesn't seem to have chance to be 1, > does it? It's depend. I'm pretty tired that discussian about bridging. So if people want to use bridge let set start_bridge to 1, if not leave it in zero. Also it's possible to setup that value at configuration stage, whatever. > And, what's the difference among those three values of > "bridge"? To diagnostic current behaviour about bridging. > > > + bridge="_bridge_on" Startup script configured do not touch bridging and at the time when script starting, bridging was enabled. > > + bridge="_bridge_off" /.../ disabled. > > > + bridge="_bridge" Script configured to setup bridging and did successfully When bridge == "" its means that kernel compiled without bridging support, or outdated kernel. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000808071546.C360>