Mageia forum

With Mageia 4, the system went to using "consistent network naming rules".

I promptly disabled that; it breaks a lot of things for me and I just don't want it on my workstation. I disabled it by making an appropriate rule in /etc/udev/rules.d, and by symlinking 80-net-name-slot.rules to /dev/null.

Now, in Mageia 5, it is back...and it is causing a lot of heartburn for me.

I have three nics on this machine. I want them named eth0, eth1, and eth2. Eth0 is always connected since it is my internet connection. Eth1 and eth2 may or may not be connected, depending on what I am doing.

Presently, neither eth1 nor eth2 were connected when I booted this machine into Mageia 5. Now, I have connected eth1 but can't use it because it is defined as enp6s0f1 while my eth2 is defined as enp6s0f0. This breaks a lot of scripts for me, and I want it the way I want it.

How can I require my nics to be named the way I want them named, even when they are not connected at boot time?

jiml8 wrote:With Mageia 4, the system went to using "consistent network naming rules".

I promptly disabled that; it breaks a lot of things for me and I just don't want it on my workstation.

My suggestion is just bite the bullet and let the borg consume you. No idea if this will help you.
http://www.freedesktop.org/wiki/Softwar ... faceNames/

jiml8 wrote:Presently, neither eth1 nor eth2 were connected when I booted this machine into Mageia 5. Now, I have connected eth1 but can't use it because it is defined as enp6s0f1 while my eth2 is defined as enp6s0f0. This breaks a lot of scripts for me, and I want it the way I want it.

I hear where you are coming from. I do clean installs on 4 different systems and they all have different systemd nic names.
My install/change scripts currently modify 53 configuration files.

My solution is a node configuration file with the node's nic names. That allows me to use a nic variable in all my scripts. I created a /var/local partition to hold my node environment values.
All my scripts sources that file. $ cat /var/local/*.env

Code: Select all

# created by /local/bin/dump_dmidecode Fri 19 Jun 13:47 2015
_sys_owner=bittwister
_net_admin=bittwister@wb.home.test
_mb_uuid="2EF807EB-95D3-5F12-53D6-311996D267D4"
_mb_name="2AB1 "
_arch=x86_64
_dist_vendor=Mageia
_dist_branch=Official
_dist_release=5
_dist_ver=2
_dist_phase=official
_ker_type=desktop
_net_nic=enp3s0
_tuner_nic=enp4s0
_wireless_nic=wlp2s0
_lan_domain_ip=192.168.11
#****** end /var/local/dmidecode.env **********************


bittwister wrote:My suggestion is just bite the bullet and let the borg consume you. No idea if this will help you.
http://www.freedesktop.org/wiki/Softwar ... faceNames/

That link might well have helped me. I have read it before, but it has been changed since I last read it. I had symlinked the 80-net-name-slot.rules, but they changed the name to 80-net-setup-link.rules, for no apparent reason.

So now I have symlinked that one too. Next time I reboot, I'll see if that fixes my problem (it should, I think, though who can say for sure?). Of course, I won't be rebooting for awhile...probably weeks...unless this particular problem bites me hard enough that I have to.

My solution is a node configuration file with the node's nic names. That allows me to use a nic variable in all my scripts. I created a /var/local partition to hold my node environment values.
All my scripts sources that file. $ cat /var/local/*.env

Yeah, I probably should consider doing something like that.

I was just forced to reboot when akonadi went berserk. Not sure whether it was the server or akonadi-baloo. Whatever...my UI crashed and I could not bring it back until I rebooted.

The reboot has given me back my eth1 and eth2, just as I want them. So symlinking that changed udev rule name did solve the problem. Now...why did they change the name?