[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Sharing network from VMWare client



Greetings,

After haveing RTFM'd relevant sources wrt host-client networking for
VMWare, I am still not able to connect to outside networks (ie www,
email, etc.) from any VM guest (curr W98).

Although the VMWare docs and Compton's "VMWare 2 for Linux" are ~very~
descriptive, they are neither informative nor ~illustrative~ about
configuring this combination to work.

Some of you may already know that VMWare accomplishes networking through
virtual interfaces. All the docs describe networking configurations that
~assume~ IP's of both physical and virtual interfaces to be on the same
subnet (or group of them). However, my setup is as follows (output from
ifconfig):

# --- start ifconfig

eth0      Link encap:Ethernet  HWaddr 00:00:B4:A2:0C:9B  
          inet addr:10.169.239.186  Bcast:10.255.255.255  Mask:255.255.255.248
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2454004 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1740188 errors:0 dropped:0 overruns:0 carrier:0
          collisions:627 txqueuelen:100 
          Interrupt:9 Base address:0xe400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:963335 errors:0 dropped:0 overruns:0 frame:0
          TX packets:963335 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

vmnet1    Link encap:Ethernet  HWaddr 00:50:56:01:00:00  
          inet addr:192.168.46.1  Bcast:192.168.46.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1221 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 

# --- end ifconfig

As you can see, my eth0 and vmnet1 (virtual interface) are on completely
different IP nets.

I believe that this is where my difficulty is in accessing the
"internet" from within a VM guest OS. 

To further complicate matters, although I have a static eth0 IP, I can't
change the IP of the vmnet1 to be within this range, as there are no
free IP's within the 10.169.239.x range (according to my ISP).

My questions are then:

1.	Would I be able to change the vmnet IP to something in the 10.x.x.x
range? Assuming that would also involve netmask changes, what would they
be?

2.	Would it be easier to us either forwarding or masquing to allow
traffic from vmnet1 access to the net through eth0?

3.	I have none of the "advanced" net packages included: ie. ipmasq,
ipchains / tables. Which of these would I need.

Also, I am running Potato2.2r5 (stock with upgrade to 2.2.20 kernel).

I would like to be able to install a 2nd Potato as a VMWare guest and
use it as a testing ground for upgrading to Woody (and for testing
source compiled apps) before installing them in my main system in the
future. However, if I can't get access to the net, I won't be able to
use apt-get and other features of Debian.

I could really use some help.

TIA,
C. Masters




Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: