What determines the assignment of eth0, eth1, eth2, etc..
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What determines the assignment of eth0, eth1, eth2, etc..
Apologioes but I don't have time to investigate - thought I'd ask here.
I've got five HP DL580s with a couple of onboard broadcom nics and an additional 4 intel nics that were also installed.
What determines which nic gets assigned to eth0, vs. eth1, vs. ethX. Is it consistent across servers? The data center guys connected only one NIC on each box - same port on each server. This consistently came up as eth6. (That's what I've been using for primary connectivity.)
Thanks!
(PS. Same OS. Save cards in same slots. Same hardware. Everything identical except for MAC addresses obviously)
Last edited by larold; 02-04-2010 at 12:06 PM.
Reason: Clarification
Have a look at the udev man page. The assigning is done using udev rules. My persistent net file looks like this:
Code:
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 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:d3:52:20:53", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:d2:2b:42:93", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.