Overview of Virtual Network Topologies

Effective management of virtual networks within VMWare Workstation is essential for establishing proper connectivity between guest operating systems, the host machine, and external networks. This guide outlines the distinct network connection types available and provides step-by-step instructions for configuring Host-Only, NAT, and Bridged modes.

Understanding Connection Types

VMWare provides several virtual network adapters, each serving a specific isolation or connectivity purpose.

1. Custom Mode

This configuration offers the highest level of isolation. Virtual machines connected to a custom network segment can communicate with eachother within that specific subnet. However, they are inaccessible from the host machine and have no route to external networks.

2. Host-Only Mode

In this setup, virtual machines and the host system reside on the same private network segment. They can communicate freely with one another, similar to a local area network (LAN). By default, there is no internet access unless network sharing is explicitly enabled on the host adapter.

3. NAT Mode (Network Address Translation)

NAT mode is often the default choice for general usage. It allows virtual machines to access external networks (such as the internet) by sharing the host's IP address. Key characteristics include:

• VMs can reach the internet via the host.
• Communication is possible between VMs, between VMs and the host, and between VMs and external resources.
• VMs utilize a private subnet IP, masking them from the physical network.
• No requirement for a unique physical IP address from the external router.

4. Bridged Mode

Bridged networking connects the virtual network adapter directly to the physical network adapter of the host. The VM appears as a distinct device on the physical LAN, obtaining an IP address from the external DHCP server. If the host network has internet access, the VM will also have direct internet access.

Implementation Guide

Configuring Host-Only Networking

1. Define the Network SegmentOpen the Virtual Network Editor within VMWare Workstation. Create a new network segment and select "Host-only" as the connection type.

2. Assign Adapter to VMNavigate to the virtual machine settings, select the Network Adapter, and choose the specific Host-only network created in the previous step.

3. Configure Guest OS NetworkInside the Linux guest, modify the network interface configuration. Below is an example using the eth0 interface:

   sudo vim /etc/sysconfig/network-scripts/ifcfg-eth0
   

   Ensure the configuration matches the subnet defined in the Virtual Network Editor. Example content:

   DEVICE=eth0
   BOOTPROTO=static
   ONBOOT=yes
   IPADDR=192.168.50.10
   NETMASK=255.255.255.0
   GATEWAY=192.168.50.1
   

4. VerificationRestart the network service and test connectivity. Ping the host machine to confirm internal connectivity. Note that external internet access will fail unless IP forwarding is configured on the host.

   sudo systemctl restart network
   ping 192.168.50.1
   

   If ping fails, verify that firewalls on both the Windows host and the Linux guest are temporarily disabled for testing.

Configuring NAT Networking

1. Setup NAT NetworkIn the Virtual Network Editor, add a new network and select "NAT" mode. Click on "NAT Settings" to define the gateway IP address. Ensure this gateway matches the configuration you will apply to the guest OS.

2. Assign Adapter to VMIn the VM settings, select the Network Adapter and choose the custom NAT network defined above.

3. **Configure Static IP (Optional)**If using a static IP, edit the interface file:

   sudo vim /etc/sysconfig/network-scripts/ifcfg-eth0
   

   Update the IP settings to align with the NAT subnet:

   DEVICE=eth0
   BOOTPROTO=static
   ONBOOT=yes
   IPADDR=192.168.80.10
   NETMASK=255.255.255.0
   GATEWAY=192.168.80.2
   DNS1=8.8.8.8
   

4. Apply and TestRestart the networking service and verify external connectivity:

   sudo systemctl restart network
   ip addr show
   ping www.example.com
   

   If connectivity fails, check the VMWare NAT and DHCP services in the host operating system to ensure they are running.

Configured Bridged Networking

1. Create Bridged NetworkIn the Virtual Network Editor, add a network and select "Bridged" mode. Choose the specific physical adapter (e.g., Wi-Fi or Ethernet) that provides internet access to the host.

2. Assign Adapter to VMSet the VM's network adapter to use the newly created bridged network.

3. Match IP SubnetThe guest OS must be configured with an IP address within the same range as the host's physical network. Check the host's IP configuration first.

   Modify the guest interface configuration:

   sudo vim /etc/sysconfig/network-scripts/ifcfg-eth0
   

   Example configuration matching a typical home router subnet:

   DEVICE=eth0
   BOOTPROTO=static
   ONBOOT=yes
   IPADDR=192.168.1.50
   NETMASK=255.255.255.0
   GATEWAY=192.168.1.1
   

4. Enable Host ServicesOn the Windows host, ensure that networking support services are active. Open the Services manager (services.msc) and verify that services related to device installation and VMWare bridging are set to Automatic or are currently running.

Configuration Checklist

To ensure successful network deployment, verify the following consistency across all layers:

• The network mode selected in the Virtual Network Editor.
• The network adapter setting within the specific Virtual Machine settings.
• The IP address, subnet mask, and gateway configured inside the guest operating system.

All three layers must align logically for traffic to flow correctly between the VM, host, and external networks.