udev: renamed network interface eth0 to rename2

Issues related to configuring your network
Post Reply
iCone
Posts: 17
Joined: 2014/09/05 12:40:00

udev: renamed network interface eth0 to rename2

Post by iCone » 2015/04/22 17:15:54

Hi,

Probably a beaten topic here but can't find a working solution so here we go.

Have a computer with dual NICs, the hardware seems to be working fine but since setting up Centos 6.6 one of the NICs just doesn't work.

dmesg | grep eth

ixgbe 0000:01:00.0: eth0: MAC: 3, PHY: 3, PBA No: 030C00-000
ixgbe 0000:01:00.0: eth0: Enabled Features: RxQ: 32 TxQ: 32 FdirHash RSC
ixgbe 0000:01:00.0: eth0: Intel(R) 10 Gigabit Network Connection
ixgbe 0000:01:00.1: eth1: MAC: 3, PHY: 3, PBA No: 030C00-000
ixgbe 0000:01:00.1: eth1: Enabled Features: RxQ: 32 TxQ: 32 FdirHash RSC
ixgbe 0000:01:00.1: eth1: Intel(R) 10 Gigabit Network Connection
udev: renamed network interface eth0 to rename2
ixgbe 0000:01:00.1: registered PHC device on eth1
ADDRCONF(NETDEV_UP): eth1: link is not ready
ixgbe 0000:01:00.1: eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
8021q: adding VLAN 0 to HW filter on device eth1
eth1: no IPv6 routers present
ixgbe 0000:01:00.1: removed PHC on eth1
ixgbe 0000:01:00.1: registered PHC device on eth1
ADDRCONF(NETDEV_UP): eth1: link is not ready
8021q: adding VLAN 0 to HW filter on device eth1
ixgbe 0000:01:00.1: eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present

ifconfig

eth1 Link encap:Ethernet HWaddr 0C:C4:7A:34:A3:31
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ec4:7aff:fe34:a331/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7702 errors:0 dropped:0 overruns:0 frame:0
TX packets:12398 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:668780 (653.1 KiB) TX bytes:15712997 (14.9 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:40127 errors:0 dropped:0 overruns:0 frame:0
TX packets:40127 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:269285411 (256.8 MiB) TX bytes:269285411 (256.8 MiB)

rename2 Link encap:Ethernet HWaddr 0C:C4:7A:34:A3:31
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ec4:7aff:fe34:a331/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8382 errors:0 dropped:0 overruns:0 frame:0
TX packets:13239 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:755932 (738.2 KiB) TX bytes:16872200 (16.0 MiB)

Contents of 70-persistent-net.rules

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x1528 (ixgbe) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0c:c4:7a:34:a3:30", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x1528 (ixgbe) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0c:c4:7a:34:a3:31", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

Contents to ifcfg-eth0

DEVICE=eth0
TYPE=Ethernet
UUID=b84c368b-63f6-45be-8b8e-eb67d70ae364
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
USERCTL=no
HWADDR=0C:C4:7A:34:A3:30
PEERDNS=yes
PEERROUTES=yes

Contents to ifcfg-eth1

DEVICE=eth1
TYPE=Ethernet
UUID=b84c368b-63f6-45be-8b8e-eb67d70ae364
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=none
IPADDR=192.168.1.33
PREFIX=24
GATEWAY=192.168.1.1
DNS1=24.92.226.11
DNS2=24.92.226.12
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth1"
USERCTL=no
HWADDR=0C:C4:7A:34:A3:31
LAST_CONNECT=1429721140

There's no config file for rename2

Pings to the IP of eth1 fail once in a while and rdp sessions are a bit erratic so believe that is conflicting with rename2 due to similar MAC addresses.

Deleted the 70-persistent-net.rules file and rebooted, no change.

What am I missing?

iCone
Posts: 17
Joined: 2014/09/05 12:40:00

Re: udev: renamed network interface eth0 to rename2

Post by iCone » 2015/04/22 18:45:28

Was able to sort out the failed pings and erratic rpd sessions.

Clicked on the Network Manager applet and disconnected "Wired Network (rename2)", that seems to have ended the conflict with eth1; no traffic being reported by ifconfig on rename2.

Still not able to use eth0 even thou is configured but not listed on ifconfig.

jscarville
Posts: 135
Joined: 2014/06/17 21:50:37

Re: udev: renamed network interface eth0 to rename2

Post by jscarville » 2015/04/24 16:12:34

Not sure but I don't think the UUID can be the same for both configs

iCone
Posts: 17
Joined: 2014/09/05 12:40:00

Re: udev: renamed network interface eth0 to rename2

Post by iCone » 2015/05/01 17:06:49

Bump, haven't been able to sort this out.

User avatar
TrevorH
Site Admin
Posts: 33221
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: udev: renamed network interface eth0 to rename2

Post by TrevorH » 2015/05/01 17:47:50

Your DHCP managed interface will try to set the default route. So will your static one since you have GATEWAY= in that too. As previously pointed out, you have the same UUID in both files though this only matters if you are using NetworkManager and if you are doing that the perhaps it's worth trying without it since it's not very good (at least on el6).
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

iCone
Posts: 17
Joined: 2014/09/05 12:40:00

Re: udev: renamed network interface eth0 to rename2

Post by iCone » 2015/05/04 19:53:22

Modified the ifcfg-eth0 file, removed the UUID and last used entries. The question now is, will the OS modify the file at boot or do I have to do some NetworkManager magic?

Post Reply