Date: Wed, 6 Sep 2000 10:12:24 +0200 From: =?iso-8859-1?Q?Michael_Lyngb=F8l?= <lyngbol@candid.dk> To: Scotty Klement <scotty@ods.ods.net> Cc: freebsd-emulation@FreeBSD.ORG Subject: Re: How to make vmware+networking working? Message-ID: <20000906101224.A71726@tigerdyr.candid.dk> In-Reply-To: <Pine.BSF.4.10.10009042359590.3396-100000@klement.dstorm.net>; from scotty@ods.ods.net on Tue, Sep 05, 2000 at 12:21:23AM -0500 References: <20000904234836.A85754@tigerdyr.candid.dk> <Pine.BSF.4.10.10009042359590.3396-100000@klement.dstorm.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 05, 2000 at 12:21:23AM -0500, Scotty Klement wrote: Hi, > 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. Jubii! Disabling "options BRIDGE", using a different/seperate subnet (192.168.254/24), make my FreeBSD box do NAT (ppp -nat ...), and use my vmnet1 IP as default gateway in Windows made it work. This is quite fine for me right now. > 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. Same thing here. Using a kernel compiled with "options BRIDGE" wont work. Haven't figured out why?! > 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 :) Thanks! :) - Michael > > > > On Mon, 4 Sep 2000, Michael Lyngbøl wrote: > > > Hi, > > > > The last couple of days I've been trying to setup networking the > > vmware2-port. No luck so far. > > > > Here's what I've done: > > > > - 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) > > > > I'm using 192.168.0/24 on my local lan. Using user-ppp to connect to > > internet. > > > > Configured "xl0": > > > > xl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 > > inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 > > ... > > > > Configured "vmnet1": > > > > vmnet1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > inet 192.168.0.20 netmask 0xffffff00 broadcast 192.168.0.255 > > ... > > > > Started ppp with the -nat option: "# ppp -auto -nat <my-conf>" > > > > Enabled ip forwarding: > > > > root@bla: sysctl -w net.inet.ip.forwarding=1 > > net.inet.ip.forwarding: 1 -> 1 > > > > > > 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?) > > > > Under FreeBSD I'm able to ping my Win95 machine (running under vmware): > > > > 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=0 ttl=32 time=32.030 ms > > ... > > > > And in Win95 I'm able to ping my FreeBSD box: > > > > ping 192.168.0.10 > > > > > > But I'm _not_ able to connect to anything outside my lan from Win95?!? > > > > > > What am I doing wrong? > > > > > > Thank you! > > > > - Michael > > > > 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?20000906101224.A71726>