Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Mar 2001 15:44:22 -0800 (PST)
From:      =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mikko@dynas.se>
To:        The Babbler <bts@babbleon.org>
Cc:        emulation@freebsd.org
Subject:   Re: vmware networking
Message-ID:  <Pine.BSF.4.21.0103041526380.287-100000@atlas.home.dynas.se>
In-Reply-To: <3AA2C728.C38E2FD2@babbleon.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 4 Mar 2001, The Babbler wrote:

> Mikko Tyolajarvi wrote:
> > 
> > In local.freebsd.emulation you write:
> > 
> > >I'm trying to get networking going with vmware under FreeBSD.
> > 
> > >I was going to set up host-only networking and use NATD to get to the
> > >Great Wide World under vmware.  This is kinda lucky since host-only is
> > >apparently the only sort of networking that vmware supports under
> > >FreeBSD.
> > 
> > Last time I installed vmware, one had to have bridging support in the
> > kernel, configure vmware for "host-only" networking, and then it Just
> > Worked(tm) - full network access from vmware after giving the guest OS
> > an IP address on the same subnet as the host OS. You can even use DHCP.
> > 
> > The port has since been changed to use netgraph to do the bridging,
> > which I assume should work without building a new kernel.  So, it
> > should work out-of-the box, without nat.
> 
> Well, it doesn't.  Any ideas on where to start?

Ok, just for the hell of it, I ripped BRIDGE out of my kernel and
deinstalled the vmware port (built new kernel, rebooted etc).  Now I
should be in the same position as you.

0.  Verify vmware port version. I'm using /usr/ports/emulators/vmware2
    (note the "2").  Makefile has PORTVERSION=2.0.3.799, PORTREVISION=1

    If you are using the "emulators/vmware" port, you're on your own,
    sorry.

1.  make install.  I get a dialog asking whether I want to use netgraph
    bridging.  Sure.  Choose "yes".  I get to enter network interface
    (happens to be "dc0" on this box).

2.  Port installs and prints a message (actually it prints lots
    of other stuff too) about running ${PREFIX}/etc/rc.d/vmware.sh start

3.  I run "/usr/local/etc/rc.d/vmware.sh start". I also run
    "/usr/local/etc/rc.d/rtc.sh start".  This should be equivalent to
    what happens at boot.

4.  ifconfig & netstat shows that I now have a "vmnet1" interface with
    address 192.168.0.1.  I'm running a 192.168.250.0 net here - I
    wonder if there is a connection.  Hmm.. nope.  The address seems
    hardcoded and ends up in /usr/local/etc/vmware/config.  I suppose
    strange thyings will happen if you are already using 192.168.0.0,
    but it should be easy enough to change.

5.  Fire up vmware with a previously installed OS, configured for
    "host-only" networking. (testing with NetBSD, much quicker than
    NT).  It comes up and believes it runs on my 192.168.250 net.

6.  Let out a big sigh of relief. Works like a charm.

That's it.  Now all you have to do is to try to figure out where you
deviate from this "golden path to success" :-)

     Good luck,
     /Mikko


 Mikko Työläjärvi_______________________________________mikko@rsasecurity.com
 RSA Security


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?Pine.BSF.4.21.0103041526380.287-100000>