Linux Virtual Machine network configuration methods and solutions to problems

A vmwarevm has just been installed for linux virtual machine network problems, and a redhatlinux operating system has been installed on it. Prepared after installation

Linux Virtual Machine network problems
I just installed a vmwarevm and installed a redhat linux operating system on it.
After the installation is complete, the following network is configured.
First, observe the network configuration on windows.
Ip: 192.168.1.109
Nemask: 255.255.255.0
Gateway: 192.168.1.1
Through these things, we can see that the virtual machine should also be in the same network segment (192.168.1.0), the same gateway (192.168.1.1)
The subnet mask should also be 255.255.255.255.0.

There are two preparation methods:
I. temporary preparation:
Configure ip address and subnet mask
Ifconfig 192.168.1.110 netmast 255.255.255.0
Configure the default gateway
Route add default gw 192.168.1.1

II. permanent preparation:
Edit the preparation file. Note that Chinese characters are comments. remove Chinese characters when editing files.
Vim/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE = "eth0" DEVICE name
HWADDR = "00: 24: 1D: 8A: 3D: F7" physical address
ONBOOT = "yes" whether to start
BOOTPROTO = "static" static IP address can select dhcp
NETWORY = "192.168.1 .. 0" network segment --! Make the same network segment as windows
IPADDR = "192.168.1.110" IP address
NETMASK = "255.255.255.0" subnet
GATEWAY = "192.168.1.1" GATEWAY--must be consistent with that on windows

Restart the Nic after preparation
Service network restart
Note that after the preceding command is executed, the network configuration will be performed according to the preparation file.

III. possible problems in network preparation:
When the preparation is complete and the NIC is restarted to execute service network restart
Failed to disable eth0 Nic
Shutting down interface eth0: Device eth0 has MAC address 00: 0C: 29: AD: 57: 66 instead of configured address 00: 24: 1D: 8A: 3D: F7.
Ignoring [FAILED]
Indicates that the eth0 Nic has a physical address 00: 0C: 29: AD: 57: 66, not the physical location of the preparation.
Address: 00: 24: 1D: 8A: 3D: F7. Ignore.
That is to say, we already have a physical address, so do not randomly configure it in the preparation file.
Therefore, the above preparation HWADDR = "00: 24: 1D: 8A: 3D: F7"
Change to HWADDR = "00: 0C: 29: AD: 57: 66". you can also find it through ifconfig.
Restart the NIC. everything is OK.

Now the network should be connected, so let's test it.
You can ping the linux virtual machine on windows 7. However, linux virtual machines cannot ping windows.
It's strange. what's going on. In general, it may be that the firewall on windows 7 has been blocked.
The solution is to disable the firewall on windows 7 and try again.
You can disable the firewall by running firewall. cpl on run.

Then ping the IP address. Call ~~ Finally solved the problem.
However, to connect to a virtual machine. Is it reasonable to close the firewall directly?
Secure?

========================================
In fact, I am doing a series of work in order to be able to access through putty on windows
Linux on the virtual machine.
Therefore, you need to create an ssh service on linux.
Command service sshd start
And does not want to execute this command every time, so it is in the root ~ /. Bash_profile preparation
File.
You only need to add a line: service sshd start.
Finally, putty can be accessed smoothly. The next time you open the VM, you do not need to configure the network, and you do not need to manually open an ssh service. this is very convenient. Use putty to connect directly to windows ,:)