I dunno what you guys are smokin. If I fire up VMWare and do ifconfig on
the host, vmnet1 is right there with his own IP, which I didn't choose.
During setup, VM sets the IP of the vmnet *module*, on the host side.
After installing Winxx "in the box", I assign the "virtual NIC" a
different IP, gateway, DNS, etc, consistent with my home network. I use a
10.x.x.x internal net, so my setup is like this:
Linux Host:
eth0 10.0.0.1
DNServer 24.93.35.65
Gateway 10.0.0.15 #my firewall
vmnet1 172.16.80.1 #configured by VM install
Win98 VM machine
AMD NIC 10.0.0.9 #assigned by me
DNServer 24.93.35.65
Gateway 10.0.0.15
VMWare calls your "virtual NIC" an AMD PCnet no matter what it really is.
VM also has its own DHCP client/driver/setup for the virtual Windows, if
you need DHCP. I had it working before I set up the firewall, but I don't
remember how it worked. IIRC, it wasn't complicated.
I've also used VM on 2.2.9, 2.2.11, RedHat 2.2.5, and now SuSE's 2.2.10
with no problem. Maybe the confusion is due to the fact that if you
recompile your kernel & modules, you have to reinstall the vmnet & vmmon
modules after the fact.
--
Doc Shipley
Network Guy
TARL Labs, UT
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
