Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
The first module to load gets to be eth0..
So the trick is to make sure your eth nic module loads before the wireless nic module.
This order is handled by hotplug and the order of lines in /etc/rc.d/rc.modules
Make sure your eth nic module is specified earlier than your wireless module.
Not exactly. They work after the loading of the driver, but not necessarily after the interfaces are up (you can put it in the boot sequence right after modprobing but before ifup/down).
Nevertheless, (assuming a recent distro) udev rules take place as the drivers are being loaded. This way, you are closest to the kernel naming scheme. And you won't get problems, if, for example you have the drivers for both NICs built-in to the kernel (instead of modules).
A lot of people compile drivers into the kernel, and then realize, that after a kernel upgrade, the internal order of loading drivers had inadvertently been switched, so the interface names are backwards. Udev rules can fix this.
FYI, my earlier writing doesn't work neither. I found out that my cards swap when I make a reboot . Nevertheless, the tip from osor seems to work and udev isn't that difficult! http://www.reactivated.net/writing_udev_rules.html has a good description on how to do it.
I used following procedure (debian, kernel 2.6):
udevinfo -a -p /sys/class/net/eth0 and
udevinfo -a -p /sys/class/net/eth1
I updated now my scripts (e.g. /etc/network/interfaces) and instead of referring to eth0 and eth1, I refer now to lan and wlan.
udev seems to me a great tool! I am looking for a strategy on how to load my modules. At the moment, it is a real mess (and I think that this is the root cause why my cards were swapping all the time). It seems to me that udev will be great help to structure my module loading. If anyone has tips or has his own strategy on module loading, they are always welcome (but maybe we can open a new thread for that)
Hi everybody, I have a similar problem, let me explain you, I have a Debian 5.0.5 64bits kernel 2.6.26-2-amd64, running over VmWare esxi 4.1, the hardware has 4 network adapters and Debian can see the 4 adapters, well my problem is that every time a shutdown the Debian with init 0 the ips change their physical port, I have tried a lot of things like the udev rules changing the names of the interfaces, I have tried also the aliases in the /etc/modprobe.d/aliases, I have also tried to give always the same MAC write them manually in vmware but nothing, every time I use "init 0" the ips change their position, another thing, if a I use init 6 the ips stay in the same place they were last time. I don't know what else to do, please help me.