SCIENTIFIC-LINUX-USERS Archives

March 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steven Haigh <[log in to unmask]>
Reply To:
Steven Haigh <[log in to unmask]>
Date:
Fri, 15 Mar 2013 11:31:01 +1100
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines)
Hi all,

This one has been going on for a while... Every time I install an 
updated kernel on this specific machine, I get a udev rule inserted in 
/etc/udev/rules.d/70-persistent-net.rules

That rule is:
# PCI device 0x10ec:0x8169 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:18:4d:79:65:47", ATTR{type}=="1", KERNEL=="eth*", 
NAME="eth1.203"

Now whats strange here is udev renames the physical ethernet adapter 
(eth0) to eth1.203 - which is (was?) a working VLAN.

So, the network config:
# cat ifcfg-eth0
DEVICE="eth0"
BOOTPROTO="static"
BROADCAST="192.168.1.255"
HWADDR="00:40:63:EA:B7:21"
IPADDR="192.168.1.1"
NETMASK="255.255.255.0"
ONBOOT="yes"

# cat ifcfg-eth1
# Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
TYPE=Ethernet
DEVICE=eth1
BOOTPROTO=static
ONBOOT=no
HWADDR=00:18:4d:79:65:47

# cat ifcfg-eth1.10
# Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
TYPE=Ethernet
DEVICE=eth1.10
BOOTPROTO=static
ONBOOT=yes
IPADDR=10.1.1.254
NETMASK=255.255.255.0
VLAN=yes
IPV6INIT=yes
IPV6_AUTOCONF=no
IPV6ADDR=2002:cb38:f71b:2::1
IPV6FORWARDING=yes

# cat ifcfg-eth1.203
# Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
TYPE=Ethernet
DEVICE=eth1.203
BOOTPROTO=static
ONBOOT=yes
IPADDR=203.56.246.94
NETMASK=255.255.255.240
VLAN=yes
IPV6INIT=yes
IPV6_AUTOCONF=no
IPV6ADDR=2002:cb38:f71b:1::1
IPV6FORWARDING=yes

As you can see, there isn't very much out of a normal ethernet setup - 
but the where the udev rule comes from is beyond me. It happens 
guaranteed every time yum installs a kernel update.

Does anyone have any pointers on where to chase this down to?

-- 
Steven Haigh

Email: [log in to unmask]
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

ATOM RSS1 RSS2