can you create symlink to /sys/class/net/"devicename" ?

Przemas · 11-12-2016, 03:28 PM

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.

BW-userx · 11-12-2016, 05:33 PM

read this to handle your device name. You can actually change it to whatever you want to call it.

https://wiki.archlinux.org/index.php..._configuration

look for this heading Change device name about mid way in the page

Przemas · 11-13-2016, 04:43 AM

thank you BW.
Tried this one:
https://wiki.archlinux.org/index.php...l_device_names

- 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.

hazel · 11-13-2016, 09:31 AM

Try passing the kernel command net.ifnames=0 on the grub boot line.

BW-userx · 11-13-2016, 02:25 PM

Quote:

Originally Posted by Przemas

thank you BW.
Tried this one:
https://wiki.archlinux.org/index.php...l_device_names

- 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?

BW-userx · 11-13-2016, 02:43 PM

on that same link I found this:

Quote:

Device names

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.