Date: Wed, 6 Sep 2000 07:13:25 -0700 From: "Vladimir Silyaev" <vsilyaev@mindspring.com> To: "Michael Harnois" <mdharnois@home.com> Cc: "Brian Beattie" <beattie@beattie-home.net>, <emulation@FreeBSD.ORG> Subject: Re: vmware2 networking question Message-ID: <000501c0180c$a0431940$e40ffea9@vt.ny.us> References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us> <86lmx6yyzq.fsf@mharnois.workgroup.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok. But those problem doesn't caused by vmware/vmnet, isn't it? I knew that such configuration works for some network cards/network drivers, in rest cases the network drivers and/or FreeBSD BRIDGE code should be fixed. Vladimir ----- Original Message ----- From: Michael Harnois <mdharnois@home.com> To: Vladimir Silyaev <vsilyaev@mindspring.com> Cc: Brian Beattie <beattie@beattie-home.net>; <emulation@FreeBSD.ORG> Sent: Tuesday, September 05, 2000 8:34 PM Subject: Re: vmware2 networking question > On Tue, 5 Sep 2000 18:42:17 -0700, "Vladimir Silyaev" <vsilyaev@mindspring.com> said: > > > You have just enable 'option BRIDGE' in your kernel. And after > > that your 'hostonly' networking in VMware guest becoming really > > bridged. > > Except it doesn't work. Perhaps it works for you, but vmware2 > networking on my machine stops working entirely until I disable the > bridge. In addition, having bridging enabled causes loops in the > bridge topology when one has more than one ethernet card in the > machine. > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > The opposite of a correct statement is a false statement. > The opposite of a profound truth may well be another profound truth. > -- Niels Bohr 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?000501c0180c$a0431940$e40ffea9>