Systemd update broke my network because I don't have ipv6

weirddan455 · 2015-04-19 23:14:05

I use a custom 4.0 kernel and I don't have ipv6 compiled into it because I don't use it. This worked fine in systemd 218 but with 219 systemd-networkd throws a hissy fit and refuses to bring up my network interface at all. Luckily I still have the Arch kernel installed so I was able to boot into that to use the network. This is also how I know for sure it's because of my kernel configuration. Is there any workaround for this?

Apr 19 18:02:25 arch systemd[1]: Starting Network Service...
Apr 19 18:02:25 arch systemd-networkd[318]: Enumeration completed
Apr 19 18:02:25 arch systemd-networkd[318]: enp7s0          : Cannot configure IPv6 forwarding for interface: No such file or directory
Apr 19 18:02:25 arch systemd-networkd[318]: enp7s0          : enp7s0          : could not bring up interface: Address family not supported by protocol
Apr 19 18:02:25 arch systemd-networkd[318]: enp7s0          : enp7s0          : could not set route: Network is unreachable
Apr 19 18:02:25 arch systemd-networkd[318]: enp7s0          : link configured
Apr 19 18:02:25 arch systemd[1]: Started Network Service.

Last edited by weirddan455 (2015-04-19 23:18:06)

bstaletic · 2015-04-19 23:58:14

I have a few (Gentoo style) workarounds.

- Recompile systemd-219 to exclude its support for ipv6. This would require reading a lot of systemd documentation.
- Recompile kernel to include its support for ipv6. since you're already familiar with custom kernels this would be the easiest. If I were to do it, this would make me annoyed (I also have a perfect fit of a kernel for my system).
- Change your init. This is officially unsupported under Arch, but not impossible.

As you can see systemd likes to say "My way, or the high way".
for a more suble/gentle solutions wait more replies.

weirddan455 · 2015-04-20 05:36:19

Those all seem pretty drastic methods haha. I'm actually on the network now with my custom kernel by simply manually bringing up the interface and adding the default route with the "ip" command. So it's not some integral part of systemd that's breaking, just the systemd-networkd.service that automatically brings my interface up at boot.

I was also able to reproduce this bug on the stock Arch kernel by adding "ipv6.disable=1" to the APPEND line in my bootloader to simulate no ipv6 support in the kernel.

I think I'll file a bug report with systemd as this definitely looks like a regression to me. In the mean time I'll just disable systemd-networkd and use netctl instead to bring up my network.

R00KIE · 2015-04-20 10:13:45

Similar (if not the same) bug already filled https://bugs.freedesktop.org/show_bug.cgi?id=90103

It will probably take some time until the devs get around to it.

Alad · 2015-04-20 10:22:41

Recompiling systemd without feature X should just be about adding the right configure flag (./configure --help).

Have you tried setting dhcp=ip4 or IPForward=ipv4 ?

http://www.freedesktop.org/software/sys … twork.html

Last edited by Alad (2015-04-20 10:23:25)

R00KIE · 2015-04-20 18:20:28

If one is using static ip configuration dhcp=ip4 doesn't help and IPForward=ipv4 is an unrelated setting.

weirddan455 · 2015-04-20 18:30:09

R00KIE wrote:

Similar (if not the same) bug already filled https://bugs.freedesktop.org/show_bug.cgi?id=90103
It will probably take some time until the devs get around to it.

Yea that's the same bug I'm running into. I don't suppose making an account to add a "me too" would help anything. Thanks for the find though. Saved me from writing a duplicate report.

R00KIE wrote:

If one is using static ip configuration dhcp=ip4 doesn't help and IPForward=ipv4 is an unrelated setting.

And yea I'm using static IP. Looks like systemd-networkd is a lost cause until they fix it.

Last edited by weirddan455 (2015-04-20 18:30:46)

R00KIE · 2015-04-20 20:02:35

Adding a me too would do no good (would just add noise), but you can still create an account and add yourself to the cc list so you can follow any replies. Later if the problem is solved for the OP but not for you then you can say something since you see what is apparently the same problem.

As a temporary workaround you can use a service file to bring the network up and configure the ip, not ideal but should work.

Alad · 2015-04-20 21:14:23

R00KIE wrote:

If one is using static ip configuration dhcp=ip4 doesn't help and IPForward=ipv4 is an unrelated setting.

Well the error message did say

Cannot configure IPv6 forwarding for interface: No such file or directory

If you have already tried to no success, I'll be silent.

weirddan455 · 2015-04-21 07:57:31

Alad wrote:

R00KIE wrote:
If one is using static ip configuration dhcp=ip4 doesn't help and IPForward=ipv4 is an unrelated setting.
Well the error message did say
Cannot configure IPv6 forwarding for interface: No such file or directory
If you have already tried to no success, I'll be silent.

That's a good point. I just tried and it didn't work though

I did get netctl set up and that's running just fine for me as a replacement for systemd-networkd.

gen2arch · 2015-04-22 11:17:58

-- mod note: this was merged in from its own thread. Trilby --

Hi

I updated to systemd 219-5 and afterwards networking was completely broken on my system.
I used to start networking by using the systemd-networkd service.
When trying to start this now, I get the following error:

could not bring up interface: Address family not supported by protocol

This is perhaps related to my command line kernel option

ipv6.disable=1

I also tried "ipv6.disable_ipv6=1" or omitting this option completely, but nothing worked.

Is systemd-networkd incompatible with this option or is it just a bug?

Thanks for your help

gen2arch

Last edited by Trilby (2015-04-22 12:16:53)

Raynman · 2015-04-22 11:36:44

https://bbs.archlinux.org/viewtopic.php?id=196338

Trilby · 2015-04-22 12:16:18

Mod note: merged in posts 11+12.

enihcam · 2015-04-24 08:21:16

Same issue here on my archlinux-based NAS router without ipv6 support. According to documentation, I changed the configuration but it does not work.

external.network:

[Match]
Name=e*

[Network]
DHCP=no
LinkLocalAddressing=no
IPForward=no ##forward to ppp0, not here##

[DHCP]
UseDNS=false
UseMTU=false

internal.network

[Match]
Name=w*

[Link]
MTUBytes=1480

[Network]
DHCP=no
Address=192.168.1.1/24
LinkLocalAddressing=ipv4
IPForward=ipv4

[DHCP]
UseDNS=false
UseMTU=false

Kotrfa · 2015-04-24 18:51:54

Same problem here.

Quick solution for me was to delete ipv6.disable=1 from kernel command line.

Last edited by Kotrfa (2015-04-26 13:11:49)

pejobo · 2015-04-25 15:53:39

> Quick solution is to delete ipv6.disable=1 from kernel command line.

No solution for me, my router has no ipv6. I configured a static profile as described here: https://wiki.archlinux.org/index.php/Dh … ic_profile

Freso · 2015-05-10 00:22:41

I've created a small custom "edit" to the systemd-networkd.service unit. Place the following code snippet in "/etc/systemd/system/systemd-networkd.service.d/ip-link-set-up.conf" (see also https://wiki.archlinux.org/index.php/Sy … n_snippets ) and be sure to change "eno1" to whatever your own network interface is called. You should be able to repeat the "ExecStartPost" line multiple times if you have several interfaces need starting.

[Service]
ExecStartPost=/usr/bin/ip link set eno1 up

Freso · 2015-06-24 09:49:05

Sorry about the necro-posting, but I thought I'd mention that https://bugs.freedesktop.org/show_bug.cgi?id=90103 has been fixed for systemd 221 which is now in [core], so if anyone else in the thread (or subscribed to it) have had hacks in place to circumvent this, these hacks can be removed again.

Arch Linux

#1 2015-04-19 23:14:05

Systemd update broke my network because I don't have ipv6

#2 2015-04-19 23:58:14

Re: Systemd update broke my network because I don't have ipv6

#3 2015-04-20 05:36:19

Re: Systemd update broke my network because I don't have ipv6

#4 2015-04-20 10:13:45

Re: Systemd update broke my network because I don't have ipv6

#5 2015-04-20 10:22:41

Re: Systemd update broke my network because I don't have ipv6

#6 2015-04-20 18:20:28

Re: Systemd update broke my network because I don't have ipv6

#7 2015-04-20 18:30:09

Re: Systemd update broke my network because I don't have ipv6

#8 2015-04-20 20:02:35

Re: Systemd update broke my network because I don't have ipv6

#9 2015-04-20 21:14:23

Re: Systemd update broke my network because I don't have ipv6

#10 2015-04-21 07:57:31

Re: Systemd update broke my network because I don't have ipv6

#11 2015-04-22 11:17:58

Re: Systemd update broke my network because I don't have ipv6

#12 2015-04-22 11:36:44

Re: Systemd update broke my network because I don't have ipv6

#13 2015-04-22 12:16:18

Re: Systemd update broke my network because I don't have ipv6

#14 2015-04-24 08:21:16

Re: Systemd update broke my network because I don't have ipv6

#15 2015-04-24 18:51:54

Re: Systemd update broke my network because I don't have ipv6

#16 2015-04-25 15:53:39

Re: Systemd update broke my network because I don't have ipv6

#17 2015-05-10 00:22:41

Re: Systemd update broke my network because I don't have ipv6

#18 2015-06-24 09:49:05

Re: Systemd update broke my network because I don't have ipv6

Board footer