Adding some random thoughts on this. First I finally was able to change the AP configuration to not do IPv6RA. That solved the immediate problem. But it was not straight forward to do and what other cases of broken IPv6 setup there is in the wild.
One thing systemd-netword was doing wrong (imo) was to take a fe80:: link local address and put this into the list of DNS servers without a interface specifier (a %<iface name> appended to the ll address). That seems to be mandatory for link local addresses to be usable and maybe the bringup would have succeeded if that were present. Generally wondering: would it make sense, that if the netplan yaml contained neither DHCP6 turned on, nor IPv6 addresses for an interface, to then add IPv6AcceptRA=no generally to the the generated config? If I read the systemd man page correctly that is the method of turning off IPv6 support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697730 Title: Long boot time due to systemd-networkd-wait-online.service failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1697730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
