can you create symlink to /sys/class/net/"devicename" ?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
can you create symlink to /sys/class/net/"devicename" ?
Can you create symlink to /sys/class/net/"devicename" in the /sys/class/net? I have an app that expects very specific name of a network interface (eth*), which on my system (not surprisingly) is a bit different ( /sys/class/net/enp11s0) - I thought that maybe a symlink would be a way to fool it.
- so I've used this command:
# ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
Sadly it does not made any difference, I still don't have "traditional" network devices name. And I'm a bit afraid of changing /etc/udev/rules.d/10-network.rules as the wiki clearly advises against changing those to ethX as it can cause problems.
Any ideas why this symlink command didn't work in my case?
I'm on Fedora 24.
- so I've used this command:
# ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
Sadly it does not made any difference, I still don't have "traditional" network devices name. And I'm a bit afraid of changing /etc/udev/rules.d/10-network.rules as the wiki clearly advises against changing those to ethX as it can cause problems.
Any ideas why this symlink command didn't work in my case?
I'm on Fedora 24.
I have done this is it great, my system was using some freeBSD name instead if wan0 so I used that to change my wifi name to wan0 and it worked like a charm.
you could google how to change your name device temporally as well, this too can be done.
think about how your device gets it name. the same way you change it. so it is not going to blow up your system.
worse case scenario is that the other apps that look for what ever name it already is, will just have to be changed to the new name you give it.
which is what by the way, that this one app is looking for that cannot be modified within that app itself?
For computers with multiple NICs, it is important to have fixed device names. Many configuration problems are caused by interface name changing.
udev is responsible for which device gets which name. Systemd v197 introduced Predictable Network Interface Names, which automatically assigns static names to network devices. Interfaces are now prefixed with en (wired/Ethernet), wl (wireless/WLAN), or ww (WWAN) followed by an automatically generated identifier, creating an entry such as enp0s25. This behavior may be disabled by adding net.ifnames=0 to the kernel parameters.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.