[systemd-devel] sshd.service fails on boot when primary listener is a bridge (br0) instead of real interface (eth0). What dependency is needed?

[Reindl Harald]

Am 12.04.2015 um 22:08 schrieb lyndat3 at your-mail.com:
> I can replicate the exact same error message, "Cannot assign requested address", in BOTH cases -- eno1 and br0 -- by simply having sshd listen on a non-existent IP, e.g. 10.1.1.1

and why in the world don't you just configure sshd to listen on 0.0.0.0 
and restrict access (if needed at all) by the firewall? 0.0.0.0 is 
available at *any* time of boot

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150412/b15fc3a4/attachment-0001.sig>