Date: Thu, 7 Sep 2000 07:50:13 -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: <001201c018da$efa9e580$f5c9aec7@vt.ny.us> References: <000501c017a3$b1995ce0$e40ffea9@vt.ny.us><86lmx6yyzq.fsf@mharnois.workgroup.net><000501c0180c$a0431940$e40ffea9@vt.ny.us><86zolly2a2.fsf@mharnois.workgroup.net><000c01c01875$dfca6f00$f5c9aec7@vt.ny.us> <868zt4lxow.fsf@mharnois.workgroup.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I think that in you case you will be have the same output from syslog even with nonactive vmnet. And the second point when you are have a bridging better to have IP address assigned only at one adapter. But again that problems doesn't have any relation to VMware. Regards, 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: Wednesday, September 06, 2000 7:53 PM Subject: Re: vmware2 networking question > On Wed, 6 Sep 2000 19:46:45 -0700, "Vladimir Silyaev" <vsilyaev@mindspring.com> said: > > > Could you describe [hardware] configuration in which vmware > > guest works without enabled bridiging, and doesn't work at all > > with enabled bridged. > > dc0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet 24.14.126.45 netmask 0xffffff00 broadcast 24.14.126.255 > ether 00:a0:cc:3d:00:ae > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none > dc1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:20:78:04:35:83 > media: autoselect (100baseTX) status: active > supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP none > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 > faith0: flags=8000<MULTICAST> mtu 1500 > gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 > vmnet1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.254.1 netmask 0xffffff00 broadcast 192.168.254.255 > ether 00:bd:4d:05:00:01 > > with bridging enabled, the syslog produces multiple entries like > > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (1) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (1) 00.10.a4.f4.a5.73 to dc1 from dc0 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.10.a4.f4.a5.73 to dc0 from dc1 (active) > -- loop (0) 00.40.d0.0e.75.a2 to dc0 from dc1 (active) > -- loop (1) 00.40.d0.0e.75.a2 to dc1 from dc0 (active) > > These messages cease with bridging disabled. > > > I did a testing with 3COM card with xl driver. It works without > > any problems. > > Then perhaps there is something in your software configuration which > has not been explained to the rest of us. > > -- > Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA > mdharnois@home.com aa0bt@aa0bt.ampr.org > Paranoids are people, too; they have their own problems. > It's easy to criticize, but if everybody hated you, > you'd be paranoid too. -- D. J. Hicks 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?001201c018da$efa9e580$f5c9aec7>