From owner-freebsd-hackers Thu Aug 3 16:35:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 95EC137B8EE; Thu, 3 Aug 2000 16:35:24 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny4-23.ix.netcom.com [198.211.16.215]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA01465; Thu, 3 Aug 2000 19:35:21 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id TAA01440; Thu, 3 Aug 2000 19:35:19 -0400 (EDT) (envelope-from vsilyaev) Date: Thu, 3 Aug 2000 19:35:19 -0400 (EDT) From: "Vladimir N. Silyaev" Message-Id: <200008032335.TAA01440@jupiter.delta.ny.us> To: rwatson@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: References: Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In muc.lists.freebsd.hackers, you wrote: > >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >bridge_in-- reading table >... > >The vmware2 port now seems to enable bridging by default, and generate a >kernel message for every ethernet packet sent. FreeBSD bridge code doesn't have any vmware related modifications. Only one modification what was impelmented, it's a special sysctl net.link.ether.bridge_refresh, which provied support for loadable ethernets drivers. The rest of bridging code didn't touched at all. >Bridging on by default may >have nasty side effects for multi-interface machines (especially security >side effects). It's several ways to work around about that: - compile kernel without bridging support. - remove bridge starting code vmware.sh file in rc.d directory. - create special bridge cluster with one real interface and with one emulated >I haven't read the code (I admit) but I finding the >current behavior both (a) irritating (messages) and (b) worrying >(unpredicted bridging with potential side effects). I don't know I never seen such effect. Could you to do more testing about that. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message