vmware network settings three: understanding the virtual network type http://www.chinaunix.net Author: yunqing Posted: 2004-07-30 07:07:33
Many friends use VMware to test different systems, I am in connection with my own experience, talk about the understanding of the network settings, please correct it. Bridge: This way is the simplest, directly connecting the virtual Net Bridge to a physical network card, and the next network card is bound to two different addresses, which actually sets the network card as a mixed mode, thus reaching multiple IPs. ability. In this mode, the network card inside the virtual machine (e.g., ETH0 under Linux) is directly connected to the network where the physical network card is located, and it can be imagined to be equal to the virtual machine and the HOST machine. It is equal to network relationship. No one is behind the problem. Using this way is simple, provided that you can get more than 1 address. For friends who want to make various network experiments are not suitable, because you can't control the network's network, it goes out. NAT: This method has a virtual network card VMNET8 in Host (by default), if you have experience in the NAT server, the VMNet8 here is equivalent to the network card connected to the intranet, and the virtual machine itself Equivalent to the machine on the intranet, the network card (ETH0) in the virtual machine (Eth0) is independent of VMNET8. You will find that VMware comes with the VMNet8 interface by default, so that the virtual machine can use DHCP services. More importantly, VMware comes with the NAT service, providing addresses from the VMNet8 to the external network, so this is a real NAT server running, just for virtual machinery. Obviously, if you only have an external network address, this method is very suitable. Hostonly: This should be the most flexible way. If you are interested, you can make a variety of network experiments. The only difference between NAT is that in this way, there is no address conversion service, so in the case, the virtual machine can only go to the host access, which is also the meaning of Hostonly's name. By default, there will be a DHCP service loaded on VMNet1. This virtual machine connected to VMNET1 can still be set to DHCP, which is convenient for the system configuration. Is there any way to connect to the external network, of course, in fact, this way is more flexible, you can use yourself The way, thus achieving the most ideal configuration, for example: a. Use your DHCP service: First stop the VMware's own DHCP service, making DHCP services more unity. b. Use your own NAT to make it easy to add a firewall. Windows Host can do NAT's way, simple, such as Windows XP Internet shares, complex, such as the NAT service in Windows Server. c. Use your own firewall. Because you can completely control VMNet1, you can join (or experiment) The firewall is between Vmnet1 and the network network. As can be seen from the above, Hostonly modes and normal NAT Server strips are similar, so you can easily perform experiments related to related experiments, such as fire and strength settings.
