Three network connection modes of Vmware

Http://virgos.javaeye.com/blog/591728

 

Many of my friends use VMware to test different systems. I will discuss my understanding of network settings based on my experience. please correct me if I am not correct.
Bridge:

 
This method is the easiest. You can directly bridge the virtual network card to a physical network card. It is similar to binding two different addresses to the next network card in Linux. In fact, you can set the network card to the hybrid mode, this allows you to listen on multiple IP addresses.

In this mode, the network card (for example, eth0 in Linux) inside the virtual machine 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 the same status, the network relationship is equal, and no one is behind it.

This method is easy to use, provided that you can get more than one address. It is not suitable for anyone who wants to conduct various network experiments, because you cannot control the network of the virtual machine and it goes out directly.
Nat mode:

 
In this way, a virtual Nic vmnet8 (by default) appears inside the host. If you have experience as a NAT server, the vmnet8 here is equivalent to a network adapter connected to the Intranet, the Virtual Machine itself is equivalent to a machine running on the Intranet, and the NIC (eth0) in the virtual machine is independent of vmnet8.

In this way, the DHCP service provided by VMware is loaded to the vmnet8 interface by default, so that the virtual machine can use the DHCP service. More importantly, VMWare comes with the NAT service, which provides address translation from vmnet8 to the Internet. Therefore, a real Nat server is running, it is only for virtual machines.

Obviously, this method is suitable if you only have one Internet address.
Hostonly:

 
This should be the most flexible method. If you are interested, you can conduct various network experiments. The only difference with Nat is that there is no address translation service in this mode. Therefore, in the case of model recognition, the virtual machine can only access the host, which is also the meaning of the hostonly name.

By default, a DHCP service is also loaded to vmnet1. In this way, the virtual machine connected to vmnet1 can still be set to DHCP to facilitate system configuration.

Is there no way to connect to the Internet in this way? Of course not. In fact, this method is more flexible. You can use your own method to achieve the best configuration, for example:
A. Use your own Dhcp Service: First stop the DHCP service provided by VMware to make the DHCP service more unified.
B. Use your own Nat to facilitate the firewall. Windows host can be used for Nat in many ways, such as Windows XP Internet sharing, and complex Nat services such as Windows server.
C. Use your own firewall. Because you have full control over vmnet1, you can add (or test) a firewall between the vmnet1 and the Internet Nic.

As you can see from the above, the hostonly mode is similar to the normal Nat server with the entire intranet, so you can easily conduct relevant experiments, such as setting a strong fire prevention.