Three Tips for using VMwareworkstation in Linux

Article Title: Three Tips for using VMwareworkstation in Linux. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

I. VMWare bridging wireless network card access is no longer limited to NAT

Environment: the host machine is UBUNTU8.04 _ amd64, VMware workstation 6.0.x

VMWare has always been widely recognized in UBUNTU (when LINUX is used as a host machine): one is the usage of sound cards, and the other is the problem of bridging wireless NICs. I have discussed a lot about the solution on the Internet, but I have never been able to solve it by using the online method. It has been bothering me for a long time (so I have been using NAT to share wireless Internet access with the host machine, but some applications have problems ). I finally figured out and solved the problem of bridging wireless network cards. I wrote it here to avoid wasting more time for later users.

Problem description: VMWare is used in LINUX. If the host uses a wireless Nic, the client Nic cannot be connected if bridging is used. According to the discussion in the VMWare Forum, if the host is windows, there is no problem because the driver supports the wireless Nic as the AP mode, and 99% won't work in LINUX. After practice, I found that it can be solved in two steps:

1. modify a file and re-compile it. Related patch files are attached.

2. The NIC configuration of the client does not select bridging. Instead, custom is selected based on the device on which the wireless Nic is bridging according to the prompt when VMWare runs config. (Note: The Bridged bridging mode is not selected, otherwise, it is impossible to connect. This is a mistake I made together with others in the past .), Select the appropriate device from the drop-down list, for example, vmnet2 is bridged to wlan0 on my machine. Therefore, select vmnet2.

2. When the host machine is LINUX and the client is LINUX, how do I switch the virtual terminal from the client?

The host and client are both LINUX. What if you want to switch the virtual terminal from the client? If you still use Ctrl + Alt + F1-F7, you will find that only the host can be switched, if you want to switch in the client to use Ctrl + Alt + space, release the space and then press the F1-F7 (note: ctrl + Alt), you can switch to the corresponding virtual terminal in the client.

3. How to add a virtual Nic?

When LINUX is used as a host machine, instead of automatically creating all the virtual NICs as a host in WINDOWS, it is generally only created as two or three virtual NICs, such as vmnet0, vmnet1, and vmnet8, if there are two bridges, there will be vmnet2. What should I do if I need other virtual NICs if I want to build an experiment network?

The method is as follows: (add vmnet5 as an example)

Modify the/etc/vmware/locations file, starting with the file:

Answer NETWORKING yes

Answer VNET_0_INTERFACE eth0

Answer VNET_8_NAT yes

Answer VNET_8_HOSTONLY_HOSTADDR 192.168.63.1

Answer VNET_8_HOSTONLY_NETMASK 255.255.255.0

Answer VNET_1_HOSTONLY_HOSTADDR 192.168.95.1

Answer VNET_1_HOSTONLY_NETMASK 255.255.255.0

Add other vmnet instances. If you need a nat service, it is defined as answer VMNET_5_nat yes. If you do not need a nat service, add:

Answer VNET_5_HOSTONLY_HOSTADDR 192.168.64.1

Answer VNET_5_HOSTONLY_NETMASK 255.255.255.0

/Etc/init. d/vmware restart

Then you can find that/dev/vmnet5 already exists and

After ifconfig

You can also find the new vmnet5 interface.