From owner-freebsd-emulation Sun Aug 6 19:45:31 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C875737B65B; Sun, 6 Aug 2000 19:45:28 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 56C7E1C5C; Sun, 6 Aug 2000 22:45:28 -0400 (EDT) Date: Sun, 6 Aug 2000 22:45:28 -0400 From: Bill Fumerola To: Nick Sayer Cc: Robert Watson , freebsd-emulation@FreeBSD.org Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000806224528.H95620@jade.chc-chimes.com> References: <398E0DC8.745E02F9@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <398E0DC8.745E02F9@quack.kfu.com>; from nsayer@quack.kfu.com on Sun, Aug 06, 2000 at 06:15:52PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 06, 2000 at 06:15:52PM -0700, Nick Sayer wrote: > I think you're overreacting slightly. I don't think he is. > 1. You are probably the only person on the planet who has a machine with both > bridging and vmware who (aparently) doesn't intend to bridge the guest > onto the connected LAN. This means that you have an opportunity to customize > the startup script rather than insist that everyone have it the way you like > it. That's nice. If I didn't turn bridging on, I don't want it on. I've been doing lots of recent ipfw testing recently and have compiled kernels with many different options that I have no intention of using just so I can test them as needed. I don't want some port turning them on by default. Lots of people just compile a kitchen sink kernel with all the firewalling options KNOWING that they can turn them on when they want them. > 3. POLA in this case is the opposite of what you think it is. People who > configure their kernels for bridging when they install vmware expect it to work > when they fire up the guest. They would be astonished if it didn't. People > bringing up vmware without bridging turned on would not see the behaviour you > castigate. I believe that everyone running vmware is in one set or the other. Except > you. I was astonished when I heard that vmware2 turned on bridgeing if it could find it. On a side note, if I was a {ports ,}security officer, I would have already either commented out the offending lines or marked the port FORBIDDEN. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message