You are not logged in.
- Topics: Active | Unanswered
#1 2015-09-21 21:38:31
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Network interface renamed after upgrade
I upgraded my Arch installation and my wired static IP network interface got renamed from eth0 to ens3 which resulted in a hang of 3 min. at boot.
I'm curious why this happened, whether I risk the same thing happening again in the future and how I can ensure that the interface names are stable (I like eth0 better than ens3).
I figured out how to fix it (by fixing the interface name in /etc/netctl/eth0, renaming the file to ens3 and disabling the old eth0 service and enabling ens3 instead).
Is netctl still the proper way to configure networking? This system was set up a while back.
Thanks for your help.
Offline
#2 2015-09-21 21:45:46
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Network interface renamed after upgrade
Offline
#3 2015-09-21 21:48:34
- Slithery
- Administrator
- From: Norfolk, UK
- Registered: 2013-12-01
- Posts: 5,776
Re: Network interface renamed after upgrade
When did you last update your system?
It's been at least a year since udev/systemd stopped using ethX network naming.
Offline
#4 2015-09-21 21:49:26
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Re: Network interface renamed after upgrade
Thanks. Any ideas why the interface name changed all of a sudden after an upgrade? I set up this install about a year ago and it never changed until now.
Offline
#5 2015-09-21 21:50:34
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Re: Network interface renamed after upgrade
When did you last update your system?
It's been at least a year since udev/systemd stopped using ethX network naming.
I set it up about a year ago but I do update on a regular basis, every couple of weeks or so. This is the first time the network interface gets renamed for me.
Offline
#6 2015-09-21 21:53:43
- alphaniner
- Member
- From: Ancapistan
- Registered: 2010-07-12
- Posts: 2,810
Re: Network interface renamed after upgrade
See also this.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
#7 2015-09-21 22:00:14
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Re: Network interface renamed after upgrade
Between netctl and systemd-networkd what should I use for configuring a static IP? Is there a preferred/recommended way?
My config is really simple, 1 wired interface, static IP.
Offline
#8 2015-09-21 22:02:52
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Network interface renamed after upgrade
Use systemd-networkd if you only require a wired connection: it is the simplest approach.
Offline
#9 2015-09-21 22:04:43
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Re: Network interface renamed after upgrade
Use systemd-networkd if you only require a wired connection: it is the simplest approach.
Do I need to also enable systemd-resolved or can I continue using a static /etc/resolv.conf which is also very simple in my case?
Offline
#10 2015-09-21 22:37:31
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Network interface renamed after upgrade
It should work without it, but I've not tried to do that.
Offline
#11 2015-09-21 23:20:19
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Re: Network interface renamed after upgrade
I'm still curious why the sudden interface rename today. Any ideas?
Offline
#12 2015-09-21 23:40:53
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Network interface renamed after upgrade
That all depends on what was in your upgrade...
Offline
#13 2015-09-22 00:15:46
- sirarch
- Member
- Registered: 2013-07-19
- Posts: 23
Re: Network interface renamed after upgrade
That all depends on what was in your upgrade...
A long list of things that I just said 'Y' to :-) Any logs to see what the last 'pacaur -Syu' did?
And it may not even be the last upgrade that caused it, it may have happened on a previous upgrade, I just didn't know it because I didn't reboot until now. I usually reboot fairly often though not after each upgrade.
Last edited by sirarch (2015-09-22 00:17:14)
Offline
#14 2015-09-22 00:19:24
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,426
- Website
Re: Network interface renamed after upgrade
Using an AUR helper is not, in this case, helpful. Read /var/log/pacman.log.
Offline