VMWare workation dual NIC configuration IP address graphics and text tutorial _vmware

A few days ago to a client to do remote project implementation, the client side of the server is Windows OS, our business operation requires the Linux OS, so the Windows OS install VMware.

However, when the IP address of the VM is configured, the problem of the dual NIC configuration IP address is encountered. Host is a dual network card, a network card connected to the intranet, a network card connected to the external network.

After groping finally put on VMware VM dual NIC configuration IP address things done, the following record of the general configuration process.

The IP address of the PS:VM two-block network card is 192.168.0.90, 192.168.3.250 respectively.

Where 192.168.0.90 is the intranet address, 192.168.3.250 is the external network address.

The 192.168.33.250 involved in this article are the IP addresses of remote machines connected by a dedicated line.

First, view the host network card and IP

First we look at the host's two-block network card with its corresponding IP address. As follows:

From the figure above, we can see the host's two-block network card, under Windows OS Display is the local connection and local connection 2, where the local connection is the external network adapter configuration, as follows:

Local Connection 2 is the intranet network card configuration, as follows:

Note: The local connection description is Yukon, and the local connection 2 description is I217-LM.

Below we start to configure the VM's NIC and IP.

Second, configure the VM network card and IP

To configure the VM network card and IP address, first we have to reconfigure the VMware NIC, as follows:

VMware's VMnet0 bridge connects to the host's local connection, the extranet network adapter.

Then we add a new network card VMnet2, and the VMnet2 Bridge to host the local connection 2, that is, intranet network card.

After the VMware two-block Nic is added, we will configure the network card for the VM as follows:

VMnet0 External network card to the VM should be the MAC address of the network card: 00:0c:29:3c:78:41.

VMnet2 External network card to the VM should be the MAC address of the network card: 00:0c:29:3c:78:4b.

After the configuration is complete, we begin to configure the VM's eth0 and eth1 network adapters as follows:

In the VM eth0 network card configured as an extranet IP address, the corresponding VMware VMNET0 network card, Gateway is 192.168.3.1.

ETH1 network card configuration within the intranet IP address, the corresponding VMware VMnet2 network card, Gateway is 192.168.0.1.

Now we are logged into the VM test with extranet connectivity, as follows:

With the above diagram, we can easily see that the VM and the extranet communication is normal.

Now we switch to the host and test the network connectivity of the VM to the host, as follows:

With the above diagram, we can easily see that the VM communicates with the host is normal.

Combined above we can clearly see that VMware's dual NIC configuration has been successful.

Third, configure the VM static route

For VM dual NIC configuration, we will find in the actual use process, if the remote host and the VM Dual network communication, it is not able to communicate, so our problem.

How do I get a remote host to communicate with this VM?

In fact, we simply need to configure a static route to the remote host on the VM.

Let's share an example where the IP address of the remote host is 192.168.33.250.

Now we're going to add a static route to the VM, as follows:

Route add-net 192.168.33.0/24 GW 192.168.0.1 Dev eth1

The order means that all packets that need to be sent to the 192.168.33.0/24 network segment are forwarded through the 192.168.0.1 Gateway and forwarded through the ETH1 network card.

Of course, if we want to remove the static route that has been added, you can use the following command:

Route del-net 192.168.33.0/24 GW 192.168.0.1

After static routes have been added, we can trace the path to the remote host via the traceroute command on the VM, as follows:

Traceroute 192.168.33.250

For CentOS, if the traceroute command is not installed, you can install it using the following command:

Yum-y Install Traceroute

With the figure above, it is easy to see that the first route from the VM to the remote host 192.168.33.250 is 192.168.0.1, which matches exactly the static route we just configured.

Next we switch to the remote host, the remote host is Windows OS, we can use the tracert command to trace the path to the VM, as follows:

Tracert 192.168.0.90

The above is a small set to introduce the VMware workation dual network card configuration IP address graphics and text tutorials, I hope to help you, if you have any questions please give me a message, small series will promptly reply to everyone. Here also thank you very much for the cloud Habitat Community website support!