Linux System network problem processing set "include VM handling"

1.1. The new operating system pings different hosts:

Check if the Linux server network segment has etho IP

View/Close Firewall

View: Service iptables status closed: Service iptables status

Close Setenforce

"More References" https://www.cnblogs.com/ftl1012/p/selinux.html

To see if the server has SSH services installed

1   ps-ef|grep ssh2   telnet-lntup 22

Check the IP of the host "real Machine"

Win7: Control Panel \ Network and internet\ network connection "see if Virtual network is turned on"

View host IP: cmd–>ipconfig

Ping each other

Change IPV4: Echo

1. Control Panel

2. Open Windows Protection Wall

3. Select the leftmost advanced settings

4. Inbound Rules

5. Locate the "Public file and print share (Echo request –icmpv4-in)" rule for the profile type, and tick on the regular inside that is enabled.

To see if a VM's service is started

CMD--Services.msc

VM Add forward "above success, ignore this operation"

1.2 Cloning virtual machines ping different hosts

Because of the cloning of virtual machines, VMware just modified the name of the virtual machine and other information, and did not modify any information on the virtual hard disk, causing the network card after cloning the MAC address and the operating system recorded in the MAC address does not match, causing eth0 to start up. The operating system records the addition of a new network card, the name Eth1,mac address of the new network card is the new MAC address assigned by VMware

Workaround:

Modify the/etc/udev/rules.d/70-persistent-net.rules file

Delete the information about eth0 in the file.

The name of the network card that modifies the second eth1 is eth0.

Modify the MAC address in/etc/sysconfig/network-scripts/ifcfg-eth0 in MAC address/etc/udev/rules.d/70-persistent-net.rules

Configuring a fixed IP for a centos virtual machine

Vim/etc/sysconfig/network-scripts/ifcfg-eth0

The following is the information of Nic Eth0

Device= "eth0" bootproto= "Static" Hwaddr= "00:0c:29:74:0b:15" ipaddr= "192.168.9.130" gateway= "192.168.9.1" netmask= " 255.255.255.0 "network=" 192.168.9.0 "nm_controlled=" yes "onboot=" yes "type=" Ethernet "uuid=" 3d8d42e3-c409-4f19-9553-aac34782711c "

Or use the new ETH1 network card directly, and get rid of hw,mac,uuid information

1.3 DNS configuration issues

1.3.1. Editing Ifcfg-eth0

1. vim/etc/sysconfig/network-scripts/ifcfg-eth0dns1= 8.8.8.8#dns2=202.106.0.20 Configuration one can be 2. Restart the Network Service/etc/init.d/network Restart3. After the configuration is complete, the DNS information is written to the/etc/resolves.conf file  cat/etc/resolves.conf4.ping www.baidu.com

1.3.2 Edit resolves.conf File

1. Edit Vim  /etc/resolv.conf   nameserver 8.8.8.8 2.ping www.baidu.com# Description: Ifcfg-eth0 is the master profile file, The information inside is written to the secondary resolv.conf, but the information written to the branch is not automatically synchronized to the overall configuration, and there is one. The system will brahma the configuration first, then find the branch file

1.4. shutting down the firewall

Temporarily closed:   service iptables stop is permanently closed:   

1.5 Remote server cannot access

Telnet 192.168.120.206

To handle this scenario:

(1) Verify that the IP address is correct?

(2) Verify that the host IP address is powered on?

(3) If the host has been started, confirm that the routing settings are set correctly? (View using the route command)

(4) If the host has been started, verify that the Telnet service is turned on on the host? (Use the Netstat command to see if TCP port 23 has a listen status line)

(5) If the host has started the Telnet service, confirm that the firewall has released 23 port access? (View with Iptables-save)

1.6. domain cannot be resolved

Telnet www.baidu.com

To handle this scenario:

(1) Confirm that the domain name is correct

(2) Confirm that the local domain name resolution is correct (NameServer is set correctly in/etc/resolv.conf, if not, you can use nameserver 8.8.8.8)

(3) Confirm that the firewall has released access to the UDP53 port (DNS uses UDP protocol, port 53, Iptables-save view)

1.7. Network large collection of ports

1. Write down the service grep-b "\b22\b"/etc/services port on the following port.   FTP port:   ssh port,   SMTP  -->sendmail Port 3306 MySQL Port 873  rsync Port 161  SNMP--  remote management device port 111  rpcbind port 3389 window Remote Desktop Port   http port 443  HTTPS Port  POP3 Port   514 DNS Port  syslog Port-   Telnet

1.8 Configuring NIC Information

1. Configuring with Setup

2. Edit Ifcfg-eth0

Vim /etc/sysconfig/network-scripts / Ifcfg-eth0

#网卡协议类型, there are Ethernet, IPSec and other types, the network interface type is Ethernet. Type=ethernet #设定物理设备别名, logical name Device=eth0 #系统启动时不激活该网络接口 [Yes|no]onboot=yes #获取地址协议 [static | bootp | dhcp | none | b OOTP]bootproto=static #IP地址IPADDR =192.168.1.254 #IP对应的子网掩码NETMASK =255.255.255.0 #IP对应的网关地址GATEWAY =192.168.1.1 #指定D NS1 Address # dns1=8.8.8.8# make DNS2 address # dns2= 202.106.0.20# when Peerdns is yes, DNS is written to/etc/resolv.conf. #指定MAC地址, you cannot use hwaddr=00:11:22:33:44:55# with MACADDR to overwrite a physically assigned MAC address, and you cannot use the # MACADDR=AA:BB:CC:DD:EE:FF#IP corresponding broadcast address with HWADDR # broadcast=192.168.1.255# the corresponding network address # network=192.168.1.0nm_controlled: #是否由Network manager controls the network interface. Changes take effect immediately after saving, without restarting. By its pit a few times, the proposal is generally set to No. #yes: Controlled by network manager #no: not controlled by Network Manager # Userctl=yes #非root用户是否允许控制这个设备 #yes: Non-root user allowed to control the interface # No: Non-root user does not run control of the network interface # srcaddr=192.168.1.254 #指定为发出去的数据包的源IP地址 # Peerdns=yes #是否指定DNS. If you use the DHCP protocol, the default is yes. #yes: If DNS is set, modify Dns#no in/etc/resolv.conf: Do not modify dns# dhcp_hostname=hostname #DHCP接收IP地址前可指定主机名 in/etc/resolv.conf # Master=bond0 #以太网接口被连接到这个接口 # Slave=yes #这个设备是否由指定在MASTER字The channel binding interface in the segment controls whether the # executes IPV6 [yes|no]ipv6init: #IPv6地址/Prefix length ipv6addr: 

3. Ifcfg-eth0 standard File

Device= "eth0" bootproto= "Static" Hwaddr= "00:0c:29:74:0b:15" ipaddr= "192.168.9.130" gateway= "192.168.9.1" netmask= " 255.255.255.0 "network=" 192.168.9.0 "nm_controlled=" yes "onboot=" yes "type=" Ethernet "uuid=" 3d8d42e3-c409-4f19-9553-aac34782711c "Dns1=8.8.8.8dns2= 202.106.0.20

4. Network card startup

Scenario One:      ifup eth0 Scenario Two:      after modifying the Ifcfg-eth0 file, the settings file onboot= "Yes" after saving the file reboot--After restarting the server, the  NIC will automatically load scenario three:      Service Network Restart           ==>/etc/init.d/network restart

5. Modify host name hostname

Temporary entry into force: hostname Ftl_lamp

Permanent entry: Vim/etc/sysconfig/network

Linux System network problem processing set "include VM handling"