<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - systemd-networkd: Add support for CANbus devices" href="https://bugs.freedesktop.org/show_bug.cgi?id=89442#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - systemd-networkd: Add support for CANbus devices" href="https://bugs.freedesktop.org/show_bug.cgi?id=89442">bug 89442</a> from <a class="email" href="mailto:mads@ab3.no" title="Mads <mads@ab3.no>"> Mads</a> <pre>I hope I'm not too spammy, but maybe I should mention that it seems that having a can device and not having IPv6 both made sure that eth0 and eth1 didn't get up. IPv6 available, no can devices present -> everything works can0 present and IPv6 available -> systemd-networkd during boot stops because of can0. Both configure and upping works if manually running `systemctl restart systemd-networkd´ afterwards, I think... can0 available and no IPv6 -> systemd-networkd stops during boot because of can0. `systemctl restart systemd-networkd´ does not work afterwards either, but that is because of lacking IPv6.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>