SSH to finally learn how to pick up addresses later is a long time demand for ssh to do that. But it is a demand for an upstream feature IMHO.
I know it can thse day's re-pickup adresses that it lost: - I have a KVM guest with one interface and I have set up ssh listen to only interface 192.168.122.221 ListenAddress 192.168.122.221 - All normal/fine. - If I take away the Network device it doesn#t work (obviously) - If I attach the device ssh without being restarted works again. But the problem here as already takled about is the fatal-fail of ssh to start if the ListenAddress not exists at the time. And network-online.target might be a help for some cases, but not e.g. for networks added much later (like my virtual network example). When I say this is a demand to upstream SSH for a long time I really mean it - this is in Ubuntu for a decade in bug 216847 and for like 3 years in upstream SSH. I think this bug here should be used to change it to network-online.target if that really helps some cases. The old bug I referred will continue to track until upstream implements IP_FREEBIND or any other late pickup tech (like listening to netlink events). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
