Three working modes of VMWare

---Network reprint

 

VMWare provides three working modes, they are bridged (bridged mode), NAT (network address translation mode) and host-only (host mode). To apply them properly in network management and maintenance, learn about these three modes of operation.
1.bridged (bridged mode)
In bridged mode, the virtualized operating system of VMWare is like an independent host in the local area network, which can access any machine in the network. In bridged mode, you need to manually configure the IP address and subnet mask for the virtual system, and it must be on the same network segment as the host machine, so that the virtual system can communicate with the host machine. At the same time, since this virtual system is an independent host system in the local area network, its TCP/IP configuration information can be manually configured to access the Internet through the gateway or router of the local area network. The relationship between the virtual system and the host machine using bridged mode is like two computers connected to the same Hub. In order for them to communicate with each other, the virtual system needs to be configured with an IP address and subnet mask, otherwise communication will not be possible. If you want to use VMWare to create a new virtual server in the LAN to provide network services for LAN users, you should choose bridged mode.
This method is the simplest. It directly bridges the virtual network card to a physical network card, which is similar to binding two different addresses to the next network card in Linux. In fact, the network card is set to promiscuous mode, so as to achieve the ability to listen to multiple IPs. In this mode, the internal network card of the virtual machine (such as eth0 under linux) is directly connected to the network where the physical network card is located. It can be imagined that the virtual machine and the host machine are in a peer-to-peer position and are equal in network relationship. There is no question of who is behind whom.
Using this method is very simple, provided that more than 1 address can be obtained.
2.NAT (Network Address Translation Mode)
Using NAT mode is to let the virtual system use the NAT (Network Address Translation) function to access the public network through the network where the host machine is located. That is to say, using NAT mode can achieve Internet access in a virtual system. The TCP/IP configuration information of the virtual system in NAT mode is provided by the DHCP server of the VMnet8 (NAT) virtual network and cannot be modified manually, so the virtual system cannot communicate with other real hosts in the local area network. The biggest advantage of using NAT mode is that it is very simple for the virtual system to access the Internet. You do not need to perform any other configuration, only the host machine can access the Internet.
This method can also achieve bidirectional access between the Host OS and the Guest OS. However, other machines in the network cannot access the Guest OS. The Guest OS can use the NAT protocol to access other machines in the network through the Host OS. The IP address configuration method in NAT mode is to allocate an IP from VMware's virtual DHCP server. The route has been set in this IP address, which points to 192.168.138.1.
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, it is recommended that you use NAT mode. In this way, a virtual network card vmnet8 (by default) appears inside the host. If you have experience as a nat server, the vmnet8 here is equivalent to the network card connected to the internal network, and the virtual machine itself is equivalent to running on For machines on the intranet, the network card (eth0) in the virtual machine is independent of vmnet8. It is found that in this way, the dhcp that comes with vmware will be loaded on the vmnet8 interface by default, so that the virtual machine can use the dhcp service. More importantly, vmware has its own nat service, which provides address translation from vmnet8 to the external network, so in this case, a real nat server is running, just for virtual machines.

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326992072&siteId=291194637