From owner-freebsd-emulation Mon Sep 4 22:21: 3 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from ods.ods.net (ip-216-145-173-167.idcnet.com [216.145.173.167]) by hub.freebsd.org (Postfix) with SMTP id D7F7137B423 for ; Mon, 4 Sep 2000 22:21:00 -0700 (PDT) Received: from [216.145.173.163] by ods.ods.net id 2a30.wrk; Tue, 5 Sep 2000 00:21:06 CDT Date: Tue, 5 Sep 2000 00:21:23 -0500 (CDT) From: Scotty Klement X-Sender: scotty@klement.dstorm.net To: =?X-UNKNOWN?Q?Michael_Lyngb=F8l?= Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: How to make vmware+networking working? In-Reply-To: <20000904234836.A85754@tigerdyr.candid.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I dont know if this is (AT ALL) helpful, but: I've managed to get vmware to work with the typical (non-bridged) host-only networking without any problems. I set up a seperate subnet for vmware (I used 192.168.254/24) and just had my FreeBSD box act as a gateway. This required me to set up a seperate IP for the vmnet1 interface, and the Windows Network configuration, and to set my vmnet1 IP as the default gateway in windows. Then, I enabled bridging by putting "options BRIDGE" in my kernel, and I changed my Windows IP (but not vmnet1) to be on my LAN's subnet, and this allowed me to see/talk to other machines on the LAN without problems, but I could no longer access the Internet. I also tried various different IP's for the vmnet1 interface, but to no avail. So, if you find a solution, please pass it along to me. :) If you need help/specifics on getting one of the two scenarios above to work, please reply, and I'll do my best :) On Mon, 4 Sep 2000, Michael Lyngb=F8l wrote: > Hi, >=20 > The last couple of days I've been trying to setup networking the > vmware2-port. No luck so far. >=20 > Here's what I've done: >=20 > - cvsup'ed and "make world" of 4.1-STABLE > - compiled a kernel including "options BRIDGE" > - installed the latest vmware2 port (vmware2/Makefile,v 1.22) >=20 > I'm using 192.168.0/24 on my local lan. Using user-ppp to connect to > internet. >=20 > Configured "xl0": >=20 > xl0: flags=3D8943 mtu 150= 0 > inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 > ... >=20 > Configured "vmnet1": >=20 > vmnet1: flags=3D8843 mtu 1500 > inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255 > ... >=20 > Started ppp with the -nat option: "# ppp -auto -nat " >=20 > Enabled ip forwarding: >=20 > root@bla: sysctl -w net.inet.ip.forwarding=3D1 > net.inet.ip.forwarding: 1 -> 1 >=20 >=20 > I'm running Windows 95 under vmware. Configured win95 to use ip address > 192.168.0.20 (same as vmnet1 - is this correct?) and setup default > gateway to 192.168.0.10 (is this correct?) >=20 > Under FreeBSD I'm able to ping my Win95 machine (running under vmware): >=20 > lyngbol@bla ~$ ping 192.168.0.20 > PING 192.168.0.20 (192.168.0.20): 56 data bytes > 64 bytes from 192.168.0.20: icmp_seq=3D0 ttl=3D32 time=3D32.030 ms > ... >=20 > And in Win95 I'm able to ping my FreeBSD box: >=20 > ping 192.168.0.10 >=20 >=20 > But I'm _not_ able to connect to anything outside my lan from Win95?!? >=20 >=20 > What am I doing wrong? >=20 >=20 > Thank you! >=20 > - Michael >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message