systemd 2.19 kills ethernet

[marlemion]

Since the update to 2.19-5 my NSA310 did not setup the enp1s0 ethernet card anymore. During boot I could see that systemd tries to setup eth0, but this is renamed by systemd itself to enp1s0.. Weird.

I am using systemd-networkd. Resolved this by reverting back to 2.18.

In my opinion, these are also results of this bug:

viewtopic.php?f=60&t=8756
viewtopic.php?f=60&t=8024 (post as regards odroid u2)

[WarheadsSE]

Huh, so you're getting enp1s0 .. sounds like the rule to keep the name @ eth0 has been moved/masked.

[marlemion]

I would really like to help, but I have very little understanding of systemd. I used to use gentoo.

Is it not normal for systemd to rename eth0 to enp1s0? And if so, where should I start searching?

[WarheadsSE]

That rename is handled via udev rules. IIRC, we had such rule masked for consistency across platforms (and confused Pi users)

[marlemion]

It has been enp1s0 since I have installed arch ~2months ago.

[Holzhaus]

I'm getting eth0 on both my ODROID-C1 and Pogoplug Series 4. The ethernet interface is only named enp1s0 on my ArchLinux desktop. So there probably something wrong with your udev rules, marlemion.