© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
It clearly affects others as a quick google will show -- if ListenAddress directive is specified then sshd fails to start citing inability to bind an address. Naively this might seem to be an unlikely case, but using DHCP to acquire a statically allocated IP address is not uncommon.
Was there any attempt to reproduce the reported problem (e.g., specify ListenAddress and reboot)?
What information is needed to get this resolved?
For future google searchers: unless someone decides to address the issue (e.g., network startup returns without waiting for DHCP so services with network dependencies are started before the network is ready and can thus fail) you have to work around this yourself. For example, assigning IP addresses statically, using IP tables to enforce restrictions, or not restricting addresses a service can use.