VMware Virtualization Networking
In this guide, you will learn how to route additional public IPs to your virtual machines even if your server has only a single authorized MAC address.
Note: Advanced virtualization networking is not covered by the standard Support Scope and requires technical experience.
View Support Scope →
The Concept: Why NAT?
Our network security blocks any traffic that doesn't originate from your main server's physical MAC address. Since VMs generate their own virtual MACs, they would be blocked in a standard "Bridged" setup.
The Solution: Your host server acts as a gateway (NAT). It accepts traffic for your additional public IPs and forwards it internally to the VMs using its own authorized MAC.
Enable Additional IPs and Forwarding
Ensure your additional IPs are active on your interface. Then, enable the kernel to pass traffic between interfaces:
Ensure your IPs are defined in your network configuration (e.g., /etc/network/interfaces) to persist after a reboot.
Set Up Routing Rules
Replace EXT-IP with your public IP and PRIVATE-IP with your VM's address:
Inside the Virtual Machine
Network Type
Set the VMware adapter to NAT or Host-Only. Host and VM must be in the same private subnet.
Example Guest Config:
IP: 192.168.219.10
Gateway: 192.168.219.1
DNS: 8.8.8.8
External Resources & Troubleshooting
Since this configuration is outside our support scope, we recommend consulting official documentation and community resources for in-depth troubleshooting and advanced network scenarios.