Date: Mon, 12 Mar 2001 16:07:51 -0800 From: Nick Sayer <nsayer@quack.kfu.com> Cc: The Babbler <bts@babbleon.org>, John Sellens <jsellens@generalconcepts.com>, freebsd-emulation@freebsd.org Subject: Re: vmware networking - really sysmouse complaints Message-ID: <3AAD64D7.4030007@quack.kfu.com> References: <200103112208.f2BM88L85365@gc0.generalconcepts.com> <20010311221123.B1541@tao.org.uk> <3AABF9DF.5E3C6E1F@babbleon.org> <20010311222703.C1541@tao.org.uk> <3AAC221F.1731699F@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > Josef Karthauser wrote: > >> On Sun, Mar 11, 2001 at 05:19:11PM -0500, The Babbler wrote: >> >>> I changed mine to use /dev/pcm0 and I still get the complaints. Not >>> that big a deal, just a minor annoyance. The fact that I can't get >>> networking working is more of a problem . . . >>> >> I don't know if you're using bridging or not... I've had problem today >> with vmware and bridging and it was because the external interface (aue0 >> in my case) wasn't in promiscious mode for some reason! I managed to >> fake it by running a 'tcpdump -i aue0' in the background. I'm sure >> there's an easier way to put the interface into promiscious mode. I'm >> not sure what it is though. > > > ngctl msg aue0: setpromisc 1 Remember, the bridging functionality also requires ngctl msg aue0: setautosrc 0 This causes the interface to not override the source Ethernet address. If you don't do this, your host and guest won't be separate machines to everyone else on the net. :-) 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?3AAD64D7.4030007>