[systemd-devel] systemd-networkd 219 chokes on can device

Mads mads at ab3.no
Wed Mar 4 01:07:52 PST 2015


I have an Atom NM10-based industrial PC with three e1000e devices and a 
PEAK can device (PCI ID 001c:0008). After updating from 216 to 219, 
systemd-networkd is unable to get my e1000e-devices up and running. I 
don't have any configuration for can0 within /etc/systemd/network.

Two files in /etc/systemd/network, 10-eth0.network and 10-eth1.network. 
System booted with net.ifnames=0. (I use a oneshot .service with some ip 
commands to up the can0-interface that worked with version 216. I can 
provide this .service if needed.)

# cat /etc/systemd/network/10-eth*
[Match]
Name=eth0

[Network]
Address=10.20.0.3/24
Gateway=10.20.0.1

[Match]
Name=eth1

[Network]
Address=10.30.0.3/24
Gateway=10.30.0.1




Here's the log from systemd-networkd both during boot (timestamp 
09:48:34) and when upping the can0 device and typing `systemctl restart 
systemd-networkd┬┤ (timestamp 09:50:53).

# journalctl -b -u systemd-networkd
-- Logs begin at ma. 2015-03-02 13:13:09 UTC, end at on. 2015-03-04 
09:50:53 UTC. --
mars 04 09:48:34 hmi02 systemd[1]: Starting Network Service...
mars 04 09:48:34 hmi02 systemd-networkd[149]: Enumeration completed
mars 04 09:48:34 hmi02 systemd[1]: Started Network Service.
mars 04 09:48:34 hmi02 systemd-networkd[149]: can0            : gained 
carrier
mars 04 09:50:53 hmi02 systemd[1]: Starting Network Service...
mars 04 09:50:53 hmi02 systemd-networkd[233]: Enumeration completed
mars 04 09:50:53 hmi02 systemd[1]: Started Network Service.
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth1            : Cannot 
configure IPv6 forwarding for interface: No such file or directory
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth0            : Cannot 
configure IPv6 forwarding for interface: No such file or directory
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth1            : eth1     
        : could not bring up interface: Address family not supported by 
protocol
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth0            : eth0     
        : could not bring up interface: Address family not supported by 
protocol
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth1            : eth1     
        : could not set route: Network is unreachable
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth1            : link 
configured
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth0            : eth0     
        : could not set route: Network is unreachable
mars 04 09:50:53 hmi02 systemd-networkd[233]: eth0            : link 
configured


The log says "link configured", but the interfaces (eth0 and eth1) are 
not in a RUNNING state even after running `systemctl restart 
systemd-networkd┬┤

The best solution would of course be full CAN device support in systemd, 
but for now.. are there some way to make systemd-networkd completely 
ignore a network device, thus making systemd 219 able to bring my eth0 
and eth1-devices up and running?

# systemctl --version
systemd 219
+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP 
-LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS 
+KMOD -IDN


- Mads


More information about the systemd-devel mailing list