https://bugzilla.suse.com/show_bug.cgi?id=1212627 https://bugzilla.suse.com/show_bug.cgi?id=1212627#c9 --- Comment #9 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Adam Majer from comment #8)

The IPv4 address is non-routable and configured via DHCP, and the only public address available is the IPv6. It's configured manually, so it's not like there is a long wait for RA or something,

I'm guessing maybe the network link is not yet ready when sshd is started. This needs detailed NetworkManager logs. To collect them, you need add the following lines in /etc/NetworkManager/NetworkManager.conf.

[logging] level=TRACE

In the "old days", all network interfaces should be configured as much as possible before the rest of the system is signaled that network is ready. So, passive configuration via RA for IPv6 would be out-of-scope for this wait but everything else should be blocking. Static IP assignments should definitely be all assigned prior to signaling network setup is successful.

Basically, I would expect all configured network interfaces to be up and configured completely before proceeding. It's not OR condition here but AND. Optionally things could proceed after some timeout, like 2 or 3 minutes, if we are waiting for external resources that may be failing (eg. DHCP)

Finally, an answer here that "it would work if you just listen on wildcard address" is not really a good answer here.

-- You are receiving this mail because: You are on the CC list for the bug.