RE: VMWare Question

["Rick Hayes" <rhayes () vicor com>]

> From the VMWare documentation...

Each virtual machine can have its own independent network configuration.
There are four choices for configuring networking: 

No networking 
Host-only networking 
Bridged networking 
Custom networking 

No networking simply means a virtual machine is run in isolation; it
will not be able to communicate with the host operating system or any
other virtual machine running on the host. This option is useful if you
desire complete isolation for testing or security purposes. To set up
your virtual machine in this way, simply do not install a network
interface adapter when configuring the virtual machine. 

Host-only networking creates a network that is completely contained
within the host computer. It is set up automatically if you select Use
Host-Only Networking in the New Virtual Machine Wizard on Windows hosts
or Host-Only Networking in the Configuration Wizard on Linux hosts. This
selection is available only if you enabled the host-only networking
option when you installed VMware Workstation. 

Host-only networking provides a network connection between the virtual
machine and the host computer, using a virtual Ethernet adapter that is
visible to the host operating system. This approach can be very useful
if you need to set up an isolated virtual network. 

If you install the proper routing or proxy software on your host
computer, you can establish a connection between the host-only virtual
Ethernet adapter and a physical network adapter on the host computer.
This allows you, for example, to connect the virtual machine to a Token
Ring or other non-Ethernet network. 

On a Windows 2000, Windows XP or Windows .NET Server host computer, you
can use host-only networking in combination with the Internet connection
sharing feature in Windows to allow a virtual machine to use the host's
dial-up networking adapter or other connection to the Internet. 

If you use host-only networking, your virtual machine and the host-only
adapter are connected to a private TCP/IP network. Addresses on this
network are provided by the VMware DHCP server. 

Bridged networking means a virtual machine runs on a virtual network
that is "bridged" to an existing physical network. This permits a
virtual machine to appear as a full-fledged host on an existing physical
network. 

A bridged virtual machine may transparently use any of the services
available on the network that it is bridged to: printers, file servers,
gateways, etc. Likewise, when a virtual machine is bridged, any physical
host -- or other virtual machine configured as bridged -- can use
resources on that virtual machine. This is the most commonly used
networking configuration. To manually configure bridged networking you
need to install a network interface adapter and mark it as "bridged".
Once the guest operating system is installed, you may then need to do
some additional configuration work that is described below. 

Custom networking refers to any network configuration other than
described above. For example, a collection of virtual machines, possibly
on multiple physical hosts, might be configured on a private virtual
network. This might be done for setting up a private file-sharing
environment or for testing a group of virtual machines in an isolated
network environment. Configuration of custom networking requires a good
understanding of networking concepts and potentially the implementation
of some simple user-level applications. Setting up custom networking is
not described in this document.  


Thanks,
Rick 

-----Original Message-----
From: Ryan [mailto:ryan () packetwatch net] 
Sent: Thursday, January 16, 2003 12:54 PM
To: honeypots () securityfocus com
Subject: VMWare Question


I was wondering if I had a computer up and running with an IP address of
192.168.1.2, and had VMWare start up another operating system would that
operating system have another IP address besides 192.168.1.2 or would
both operating systems have the same IP?

Ryan