Date: Wed, 2 Aug 2000 19:41:17 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: ports@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org Subject: vmware changes result in nasty bridging mess Message-ID: <Pine.NEB.3.96L.1000802193745.97709C-100000@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1000802193745.97709C-100000>