Network Working Mode in Vmware VMWare provides three working modes: bridged (bridging mode), NAT (network address translation mode), and host-on ly (host mode ). To apply them properly in network management and maintenance, you should first understand the three working modes. Www.2cto.com 1. bridged (bridging mode) In this mode, VMWare virtualizes the operating system like an independent master machine in the LAN, which can access any machine in the network. In the bridge mode, you need to manually configure the IP address and subnet mask for the virtual system, and also need to be in the same network segment as the host machine, so that the virtual system can communicate with the host machine. At the same time, because this virtual system is an independent host system in the LAN, You can manually configure its TCP/IP configuration information to access the Internet through the LAN gateway or router. Www.2cto.com uses the Bridge Mode to connect the virtual system to the host machine, just like connecting two computers on the same Hub. If you want them to communicate with each other, You need to configure the IP address and subnet mask for the virtual system. Otherwise, the communication will fail. If you want to use VMWare to create a virtual server in the LAN to provide network services for LAN users, you should select the bridge mode. 2. host-on ly (host mode) requires that the real environment and virtual environment be isolated in some special network debugging environments. In this case, you can adopt the host-on ly mode. In host-only mode, all virtual systems can communicate with each other, but the virtual system and the real network are isolated. Tip: in host-on ly mode, the virtual system and the host machine system can communicate with each other, because the two machines are connected through twisted pair wires. In host-on ly mode, the TCP/IP configuration information of the virtual system (such as the IP address, gateway address, and DNS server) is created by VMnet1 (host-on ly) DHCP servers in the virtual network are dynamically allocated. If you want to use VMWare to create a virtual system isolated from other machines in the network and perform some special network debugging, you can select the host-on ly mode. Watch: VM access method 1. when installing the operating system on a VM, set the system IP address to 192.168.0.99 and DNS to 192.168.0.1 2. modify the VMnet1 ip address of the VM to 192.168.0.1 3. set Internet Connection Sharing on the network card that you can access the network. The specific setting method is: properties --> advanced --> connection sharing, and then select VMnet1 to share the network with it. 4. ping 192.168.0.99 on the local machine. If the ping succeeds, it indicates that you have set it correctly. 5. go to the linux operating system in your virtual machine and surf the Internet. www.2cto.com 3.NAT( network address translation mode) uses the NAT mode, which enables the virtual system to use the NAT (Network Address Translation) function, access the Internet through the network of the host machine. That is to say, you can use the NAT mode to access the Internet in the virtual system. In NAT mode, the TCP/IP configuration information of the virtual system is provided by the DHCP server of the VMnet8 (NAT) Virtual Network and cannot be modified manually, therefore, the virtual system cannot communicate with other real hosts in the local area network. The biggest advantage of using the NAT mode is that it is very easy for the virtual system to access the Internet. You do not need to configure any other configurations, but only need the host machine to access the Internet. If you want to use VMWare to install a new virtual system, you can directly access the Internet without any manual configuration in the virtual system. We recommend that you use the NAT mode. Tip: the above mentioned VMnet8 Virtual Network in NAT mode, VMnet1 Virtual Network in host-on ly mode, and VMnet0 Virtual Network in bridged mode, they are all generated based on the automatic configuration of the vmwarevm and do not need to be set by the user. VMnet8 and VMnet1 provide DHCP services, while VMnet0 does not.