[Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel
Simon Fels
simon.busch at canonical.com
Wed Sep 14 10:44:57 UTC 2016
Yes, the kernel has IPv6 support enabled so socket_ipv6_is_supported()
returns true and with that it tries to setup the IPv6 part of the
interface.
The two problems which I've found so far are:
- an empty IFLA_AF_SPEC seems to cause the kernel to return EINVAL
- having IPv6 enabled and IFLA_AF_SPEC is filled with the ipv6ll mode we get EINVAL
So to fix this we have to do two things:
1. disable IPv6 support in the 3.4 kernel; if that is not acceptable for the real product later than we have to find another solution.
2. move the open/close_container() inside the if() statement to avoid an empty container.
For 2. we may can work around this on the kernel side too to allow empty
IFLA_AF_SPEC containers.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623068
Title:
Networkd fails to configure a ethernet network device on a 3.4 kernel
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Knowing that a 3.4 based kernel is unsupported we have to get it
working for a specific customer.
Systemd itself boots up nicely already but networkd fails to configure
a network device with the following configuration file in
/etc/systemd/network
$ cat /etc/systemd/network/enp1s0.network
[Match]
Name=enp1s0
[Network]
DNS=8.8.8.8
Address=192.168.178.30
Gateway=192.168.178.1
This gives the following error messages
$ sudo /lib/systemd/systemd-networkd
Enumeration completed
enp1s0: Could not bring up interface: Invalid argument
enp1s0: Could not set route: Invalid argument
ifupdown or NetworkManager is reliable able to get the same interface
up and configured.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions
More information about the foundations-bugs
mailing list