Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
We have SLES 10 linux. We have 3 network cards 1 Realtek (on-board ) and 2 Intel Cards (add-ons ). When we install the system , we have noticed that system detects 3 cards as
eth0 - INTEL
eth1 - Realtek
eth2 - INTEL
Now what we expect is eth0 should be assigned to REALTEK. So we are running a script which modifies the /etc/udev/rules.d/30-net_persistent_names.rules file
as per our requirement. And do /etc/init.d/network restart. But ifconfig still shows the older assignments. Like eth0 - INTEL , eth1 - realtek and eth2 - INTEL.
Now the question is how to update the ifconfig assignments without reboot. Reboot may solve this problem but we wish to achieve it without reboot.
Is there anything we need to do with udev or so ?
Thanks for the reply. We tried this command , it works fine if we have only single ethernet interface. But in case of multiple interfaces, when the interfaces names are changed in /etc/udev/rules.d/30-persistent file and udevtrigger is ran .. this command does create some weird entries for interfaces. Like ethxx0 or ethxx1.
It creates such interfaces only when we have multiple interfaces and we change the 30-persistent file manually to make eth0 to eth2 and/or eth2 to eth1. Then i guess udevtrigger gets confused and creates such interfaces.
I would change your rules to create completely differently named network devices, like realtek0, intel0, intel1 and so on, so that udev doesn't trip out. Solaris does something similar, naming the network devices according to the driver name.
You have a point. I did think that when udevtrigger tries to change the interface name from eth0 to eth2 , actually eth2 is already reserved for some interface and thats where the problem starts and i suppose then the system assigns the interface name as ethxx1 or so.
So i guess if we give some logical names then changing it will not be a problem for udevtrigger.
Sounds good , i shall give it a try and revert. For the moment , i say thanks to you for your views.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.