Unable to activate network interface

Issues related to configuring your network
LatikerBrian
Posts: 2
Joined: 2018/01/04 19:41:11

Unable to activate network interface

Postby LatikerBrian » 2018/01/04 19:55:25

I am trying to get a computer connected to the network.
However, the network cards won't "activate"
Running: CentOS 7 - Freash Install

[root@Back001 ~]# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::21d:9ff:fef1:2fb9 prefixlen 64 scopeid 0x20<link>
ether 00:1d:09:f1:2f:b9 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 270 bytes 49844 (48.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.211 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::21d:9ff:fef1:2fba prefixlen 64 scopeid 0x20<link>
ether 00:1d:09:f1:2f:ba txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 71 bytes 6057 (5.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 65 bytes 7280 (7.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 65 bytes 7280 (7.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:67:e4:23 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:67:e4:23 txqueuelen 500 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@Back001 ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 eth1
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0


[root@Back001 ~]# ping 192.168.0.1 -I eth0
ping: Warning: source address might be selected on device other than eth0.
PING 192.168.0.1 (192.168.0.1) from 192.168.0.211 eth0: 56(84) bytes of data.
From 192.168.0.211 icmp_seq=1 Destination Host Unreachable
From 192.168.0.211 icmp_seq=2 Destination Host Unreachable
From 192.168.0.211 icmp_seq=3 Destination Host Unreachable
From 192.168.0.211 icmp_seq=4 Destination Host Unreachable

Jan 04 10:49:45 Back001.internal.usapresort.com dhclient[5426]: DHCPDISCOVER on
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <warn> (et
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> (et
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> (et
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> (et
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> (et
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> Net
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> Dis
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <warn> (et
Jan 04 10:49:50 Back001.internal.usapresort.com NetworkManager[773]: <info> (et
Jan 04 10:49:50 Back001.internal.usapresort.com avahi-daemon[644]: Withdrawing a
Jan 04 10:49:50 Back001.internal.usapresort.com network[5253]: Bringing up inter
Jan 04 10:49:50 Back001.internal.usapresort.com network[5253]: [FAILED]


HWADDR=00:1D:09:F1:2F:B9
TYPE=Ethernet
BOOTPROTO=dhcp
#BOOTPROTO=static
#IPADDR=192.168.0.210
#NETWORKMASK=255.255.255.0
#GATEWAY=192.168.0.1
#NM_CONTROLLED=no
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
#IPV4_FAILURE_FATAL=no
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
#IPV6INIT=yes
#IPV6_AUTOCONF=yes
#IPV6_DEFROUTE=yes
#IPV6_PEERDNS=yes
#IPV6_PEERROUTES=yes
#IPV6_FAILURE_FATAL=no
NAME=eth0
UUID=8c8980ff-487b-488d-bffb-705c0e28a268
ONBOOT=yes

# Generated by NetworkManager
search internal.usapresort.com


# No nameservers found; try putting DNS servers into your
# ifcfg files in /etc/sysconfig/network-scripts like so:
#
# DNS1=xxx.xxx.xxx.xxx
# DNS2=xxx.xxx.xxx.xxx
# DOMAIN=lab.foo.com bar.foo.com
nameserver 8.8.8.8
nameserver 8.8.4.4


Any ideas?

User avatar
TrevorH
Forum Moderator
Posts: 21481
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Unable to activate network interface

Postby TrevorH » 2018/01/04 23:24:18

Are you aiming to use this for virtualization purposes? If not then you have some virbr* interfaces there that are created by libvirt and (probably) gnome-boxes. If you're not aiming to use that then uninstall them and reboot and the virbr* interfaces should be gone.

Otherwise you have no default route set up. Your 192.168.0.211 ip address is on eth1 not eth0 so forcing ping to try to use eth0 is a bad move. You appear to have only posted the config file for eth0 but that adapter appears to be unused. Try running ethtool eth0 and see if the last line of output says it has a link or not. Repeat for eth1. It would appear to me that your active interface is eth1 but ethtool will tell you which one has a cable connected.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

LatikerBrian
Posts: 2
Joined: 2018/01/04 19:41:11

Re: Unable to activate network interface

Postby LatikerBrian » 2018/01/04 23:43:11

First, the machine will host virtual servers, after I get the machine
connected to the network.

Second, ethtool eth0 and ethtool eth1 both returned linked: yes.
cables are plugged in to BOTH ports.

> Otherwise you have no default route set up. Your 192.168.0.211 ip address
> is on eth1 not eth0 so forcing ping to try to use eth0 is a bad move.
I get the same response with a straight ping, or using eth1.
I trying to make sure the problem is not a routing problem.

I have tried to activate the interface with nmcli. just drops.
eth1 is setup for a static ip address.

Also, I have swapped the cables with a known good cable.
I can ping the gateway from another server.