CentOS7网络设置修复
Posted
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了CentOS7网络设置修复相关的知识,希望对你有一定的参考价值。
参考技术A 服务器有两个网卡enp7s0和enp8s0服务器需要通过enp8s0和互联网联通,互联网为笔记本转接
通过centos7界面修改ip,失败;
通过centos7的网络配置文件/etc/sysconfig/network-scripts/ifcfg-enp8s0修改ip设置
设置如下:
1.启动 service network start 报错,通过journalctl -xe查看如下
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fprintd.service has begun starting up.
12月 29 19:31:12 crrchost dbus-daemon[851]: dbus[851]: [system] Successfully activated service 'net.reactivated.Fprint'
12月 29 19:31:12 crrchost dbus[851]: [system] Successfully activated service 'net.reactivated.Fprint'
12月 29 19:31:12 crrchost systemd[1]: Started Fingerprint Authentication Daemon.
-- Subject: Unit fprintd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fprintd.service has finished starting up.
--
-- The start-up result is done.
12月 29 19:31:12 crrchost fprintd[6685]: Launching FprintObject
12月 29 19:31:12 crrchost fprintd[6685]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
12月 29 19:31:12 crrchost fprintd[6685]: ** Message: entering main loop
12月 29 19:31:18 crrchost polkitd[835]: Operator of unix-session:1 successfully authenticated as unix-user:windfarm to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus
12月 29 19:31:18 crrchost systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has begun starting up.
12月 29 19:31:18 crrchost network[6693]: 正在打开环回接口: [ 确定 ]
12月 29 19:31:18 crrchost network[6693]: 正在打开接口 enp7s0:
12月 29 19:31:24 crrchost network[6693]: 正在确定 enp7s0 的 IP 信息...失败:不存在链接。检查电缆?
12月 29 19:31:24 crrchost network[6693]: [失败]
12月 29 19:31:24 crrchost network[6693]: 正在打开接口 enp8s0: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: [ 确定 ]
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost network[6693]: RTNETLINK answers: File exists
12月 29 19:31:25 crrchost systemd[1]: network.service: control process exited, code=exited status=1
12月 29 19:31:25 crrchost systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
12月 29 19:31:25 crrchost systemd[1]: Unit network.service entered failed state.
12月 29 19:31:25 crrchost systemd[1]: network.service failed.
12月 29 19:31:25 crrchost polkitd[835]: Unregistered Authentication Agent for unix-process:6669:319312 (system bus name :1.263, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale zh_CN.UTF-8) (d
3.systemctl status network.service查看如下:
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since 六 2018-12-29 18:38:17 CST; 1min 24s ago
Docs: man:systemd-sysv-generator(8)
Process: 909 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
12月 29 18:38:06 crrchost systemd[1]: Starting LSB: Bring up/down networking...
12月 29 18:38:06 crrchost network[909]: 正在打开环回接口: [ 确定 ]
12月 29 18:38:06 crrchost network[909]: 正在打开接口 enp7s0:
12月 29 18:38:12 crrchost network[909]: 正在确定 enp7s0 的 IP 信息...失败:…?
12月 29 18:38:12 crrchost network[909]: [失败]
12月 29 18:38:17 crrchost network[909]: 正在打开接口 enp8s0: [ 确定 ]
12月 29 18:38:17 crrchost systemd[1]: network.service: control process exi...=1
12月 29 18:38:17 crrchost systemd[1]: Failed to start LSB: Bring up/down n...g.
12月 29 18:38:17 crrchost systemd[1]: Unit network.service entered failed ...e.
12月 29 18:38:17 crrchost systemd[1]: network.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
1.参考网络方法停用NetworkManager,依旧报错
systemctl stop NetworkManager
systemctl disable NetworkManager
2.比对两个网卡的MAC地址和配置文件的MAC地址
a.查看mac地址配置,ipconfig
b.查看配置文件中的macd地址是否匹配,ifcfg-enp8s0和ifcfg-enp7s0,
按照网络方法增加一行HWADDR=ipconfig查询到的对应网卡MAC地址;
c.重启network服务依旧报错;
3.通过GUI界面查看网络,提示“系统的网络服务与此版本的网络管理器不兼容”
这与之前停掉NetworkManager有关,此处不表;
4.因为ifcfg-enp7s0实际上没有插网线,修正其配置文件如下:
ONBOOT=no
重新启动服务后网络正常;
5.检查网络
1.network 和NetworkManager不同,通过界面和通过配置文件,可能会导致配置混乱,且NetworkManager有些程序不支持,需要停用;
2.BOOTPROTO=none 虽然可以表示静态ip,但是如果要启用,必须设置其为
BOOTPROTO=static 或BOOTPROTO=dhcp
3.一个网卡没哟被启用,也就是没有设置动态ip或静态ip,是无法被初始化的,不能设置ONBOOT=yes
In Centos7.0 disabling NetworkManager will leave a dhcp client running configured for NetworkManager. This causes the error message RTNETLINK answers: File exists when the network service is started.
The stale dhclient process has the additional "benefit" that when the lease expires your dhclientwill choke, since it cannot reach NetWorkManager, thus removing your IP address.
If you grep for it, you will see that it points to a NetWorkManager configuration file.
[root@host ~]# ps -ef | grep dhc
root 1865 792 0 Apr28 ? 00:00:00 /sbin/dhclient -d -sf \
/usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eno1.pid -lf\
/var/lib/NetworkManager/dhclient-c96e56d3-a4c9-4a87-85ca-93dc0ca268f2-eno1.lease\
-cf /var/lib/NetworkManager/dhclient-eno1.conf eno1
So what you can do is kill the dhclient and only then start your network service.
Centos6.5网络配置
参考技术A 三种网络类型的区别在于说下虚拟机网络配置的解决方案及思路
Bridge桥接方式(首选)
与宿主机地位同等,享有真实网络ip,与物理机一样对待即可(可以模拟出一块虚拟的网卡,让他有独立的IP和mark地址可以访问外网)。
缺点:网络环境一旦改变,所有的虚拟机环境也要随之改变。
NAT方式
优点:隔离网络环境(公司与家里的网络环境切换,虚拟机的所有配置不变),与外界网络环境是隔离的。同时共享本机的真实网卡和IP地址可以连接外网。
缺点:外部机器无法访问虚拟机
hostonly不建议使用 用的是VMnet1网卡,支持虚拟机之间的互联和本机的互联,不能访问外网。
VMware-workstation12、CentOS-6.5-i386-minimal(安装linux就不在这说了)
0、首先确保虚拟网卡(VMware Network Adapter VMnet8)是开启的,然后在windows的命令行里输入“ipconfig /all”,找到VMware Network Adapter VMnet8的ipv4地址(例如:192.168.1.1);
1、首先查看虚拟网络编辑器, 步骤:编辑-->虚拟网络编辑器。能在我的windows系统上能ping通虚拟机模拟的Linux系统,选择的是桥接模式
2、检查CentOS的网络适配器的网络连接方式,如下图
3、动态配置
终端中输入“vi /etc/sysconfig/network-scripts/ifcfg-eth0 ”
动态配置——————
DEVICE=eth0
BOOTPROTO=dhcp
TYPE=Ethernet
ONBOOT=yes(开机自启动)
HWADDR=xx:xx:xx:xx:xx:xx (网卡mac地址,不用改)
重启一下service network restart
然后在终端中“ping www.163.com”查看返回信息
4.默认IP地址获取
5.静态配置——————
vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
HWADDR=00:0C:29:C6:D8:97
TYPE=Ethernet
UUID=851e47f4-2a08-4a8d-b045-3712c1998091
NM_CONTROLLED=yes
ONBOOT=yes #设置为开机启动
BOOTPROTO=static #设置为静态的ip
BROADCAST=192.168.1.255 #要和VMnet8中的ip段保持一致,最后一位必须为255
IPADDR=192.168.1.126#该虚拟机的ip
NETMASK=255.255.255.0 #子网掩码,
GATEWAY=192.168.1.1 #对应vmnet8的网关地址注意:Linux里边的网关和本地的不一致(192.168.1.1),则会出现能ping通我的本机ip,却ping不通网关的错误.
保存退出后,在终端中输入“service network restart”重启网络服务,然后在终端中“ping www.163.com”查看返回信息
参考: CentOS---网络配置详解
关于connect: network is unreachable 问题的解决
以上是关于CentOS7网络设置修复的主要内容,如果未能解决你的问题,请参考以下文章