Ethernet interface did not come up after a reboot

Issues related to hardware problems
Post Reply
Whoever
Posts: 1357
Joined: 2013/09/06 03:12:10

Ethernet interface did not come up after a reboot

Post by Whoever » 2013/12/11 15:54:50

After a reboot, one of the interfaces on my system did not come up as expected. This system has 3 interfaces, eth1 came up, eth2 came up as a different physical device to the one I expected and eth0 is missing. However, ifconfig-a shows this device:

Code: Select all

__tmp1870600612 Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:8390268 errors:0 dropped:114 overruns:0 frame:0
          TX packets:10920582 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1734134744 (1.6 GiB)  TX bytes:2286665191 (2.1 GiB)
.....
"__tmp1870600612" ???? Where do I start looking to understand what caused this?

This system has a Realtek Ethernet device which has not always come up as expected:
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

lsmod shows the r8169 module loaded, despite it being blacklisted:

Code: Select all

# lsmod | grep r8
r8169                  43077  0 
mii                     9409  1 r8169
r8168                 224724  0 
# cat !$
cat /etc/modprobe.d/blacklist-r8169.conf
blacklist r8169

User avatar
Super Jamie
Posts: 310
Joined: 2014/01/10 23:44:51

Re: Ethernet interface did not come up after a reboot

Post by Super Jamie » 2014/01/11 00:57:19

When drivers are loaded, all devices have a ___tmpXXX name, and are later renamed to ethX based off modprobe.conf or the HWADDR in the ifcfg-ethX files.

It sounds like you have a conflict between modprobe and ifcfg, or that device is not addressed for renaming at all.

Post Reply