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.
It hit me that I didn't provide a full debug-loglevel debug with
everything custom disabled. So I created a bugreport at
https://bugs.freedesktop.org/show_bug.cgi?id=89442. Please do tell if
there's anything else I should provide.
--- a/src/network/networkd-manager.c 2015-02-11 17:30:31.800897770
+0100
+++ b/src/network/networkd-manager.c 2015-03-04 15:06:42.091892185
+0100
@@ -322,6 +322,10 @@
switch (type) {
case RTM_NEWLINK:
+
+ if (strcmp("can0", name) == 0)
+ return 0;
+
if (!link) {
/* link is new, so add it */
r = link_add(m, message, &link);
@@ -347,6 +351,9 @@
break;
case RTM_DELLINK:
+
+ if (strcmp("can0", name) == 0)
+ return 0;
link_drop(link);
netdev_drop(netdev);
Any tips for what I'm missing here to create a workaround making
systemd-networkd not consider can0 as a network device would also be
appreciated :)
- Mads
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
