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

[lyndat3 at your-mail.com]

On Sun, Apr 12, 2015, at 12:49 PM, Lennart Poettering wrote:
> Hmm? why that? why does sshd care?

Iiuc, sshd's LISTENER ip's must exist & be available

I am not having sshd listen on 0.0.0.0.  I am specifying that it listens on 192.168.1.1

> What precisely fails?

I don't KNOW precisely, other than what I shared in my original post

journalctl -b | grep -i sshd
		...
		Apr 10 15:30:49 xen01 sshd[1345]: error: Bind to port 22 on 192.168.1.1 failed: Cannot assign requested address.
		...

sshd.service seems like it's trying to launch sshd BEFORE that interface -- defined in br0 config -- is available.

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

> I mean, if
> the ip addres 192.168.1.1 is bound to a local interface, then sshd
> really should work, it shouldn't matter what kind of interface that
> is.

It's bound to an EXTERNAL, interface eno1 (or br0) -- attached in this case to the LAN.

The only internal interface, 'lo', has 127.0.0.1 & :: bound.

LT