From owner-freebsd-ports Wed Aug 2 16:41:24 2000 Delivered-To: freebsd-ports@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8F33D37B5F4; Wed, 2 Aug 2000 16:41:19 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id TAA97946; Wed, 2 Aug 2000 19:41:17 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 2 Aug 2000 19:41:17 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: ports@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org Subject: vmware changes result in nasty bridging mess Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. Bridging on by default may have nasty side effects for multi-interface machines (especially security side effects). 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). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message