On Sat, Apr 06, 2013 at 07:11:46PM +0700, Pandu Poluan wrote:
>
> Ahhh... I think now I understand...
>
> So. Here's my summarization of the situation:
>
> * The ethX naming can change, i.e., the interfaces can get out of order
> * So, to fix this, udev decided to use the physical attachment points of
> the NIC in driving a persistent name, a name that will be identical across
> boots as long as there is no hardware change
> * In doing so, it also frees the 'traditional' ethX names to be used
> * If one wants, one can still 'rename' the NICs to the 'traditional' names
> using the 70-*.rules script
> * Doing so (specifying the NICs' names using the 70-*r.rules script) will
> also disable the new 'persistent naming' system -- for the NICs specified
> in the 70-*r.rules file
> * Therefore, users that will be impacted are those that upgraded udev but
> doesn't have the 70-*r.rules, for udev will then assign new names for the
> NICs
> * For these users, specifying the net....something switch for the kernel
> (sorry, forgot the complete switch) will disable the new naming system
>
> So, have I gotten everything correctly?
Works for me...
mingdao@router ~ $ cat /etc/udev/rules.d/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:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="68:05:ca:03:05:5d", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x10d3 (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="68:05:ca:03:05:50", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth1"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="f4:6d:04:e8:1d:d9", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth2"
mingdao@router ~ $ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN
link/ether f2:58:cb:48:72:b3 brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 68:05:ca:03:05:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.54.1/24 brd 192.168.54.255 scope global eth0
4: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 68:05:ca:03:05:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.100.1/24 brd 192.168.100.255 scope global eth1
5: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether f4:6d:04:e8:1d:d9 brd ff:ff:ff:ff:ff:ff
inet <public IP> brd <munged> scope global eth2
If these NICs don't get assigned correctly, this whole LAN fails.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
[email protected]
662-269-2706 662-205-6424
http://happypenguincomputers.com/
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
