5 ms·

You also need to change the boot behavior of sshd to wait for wireguard (tailscale in my case) to be available. I had to add a couple of lines to the ssh system

You also need to change the boot behavior of sshd to wait for wireguard (tailscale in my case) to be available. I had to add a couple of lines to the ssh systemd unit.

codetrotter 2y ago
Yep. And also pay attention during package and system upgrades on some systems. In certain cases it messes up this ordering, and you end up with sshd starting before Wireguard again and then sshd doesn’t find any interface with the specified address, which in turn makes it so that it won’t bind to that address. Making the machine unreachable until you manually fix it again.
- napkin 2y ago
  A less finnicky approach would be binding to 0.0.0.0, then configuring incoming firewall policy. By default deny, then allow SSH through wireguard network. Or by default allow then deny SSH through public network.
  - codetrotter 2y ago
    I like that idea a lot. I may start doing that.
    - semi 2y ago
      if you want to get fancy and/or over engineered you would use systemd templated units to setup sshd@.service and a ListenAddress in the config listening on %i. Then you could bring up sshd@(expectedip).service for each expected IP .. but that doesn't gain all that much tbh.if anything the only hesitation I'd have on listening to * and relying on firewall rules is if the service comes up before its configured. but exposing sshd isn't even that bad
- sureglymop 2y ago
  Yeah I would do it with nftables so you don't have to change the sshd listen address.
- RealStickman_ 2y ago
  You can create an override file for sshd to avoid issues due to package config changes. https://www.freedesktop.org/software/systemd/man/latest/systemctl.html#edit%20UNIT%E2%80%A6 https://www.freedesktop.org/software/systemd/man/latest/syst...
  - codetrotter 2y ago
    I did something like that but somehow after an upgrade I still lost access to one of my systems that I had set up like that. This machine is physically in a different city from me so I rarely have the chance to go there. And lately I’ve even been in another country.
eyegor 2y ago
Why don't you just add sshd restart as an interface PostUp step in the client's wireguard config file?
- kardos 2y ago
  So allow sshd to start in a failed mode and then restart it?
- inbetween 2y ago
  it only takes 3 lines in a systemd override fille (which I think don't suffer the overwrite-on-upgrade problem). To my mind, that keeps the startup logic nicely local in service files.

You also need to change the boot behavior of sshd to wait for wireguard (tailscale in my case) to be available. I had to add a couple of lines to the ssh systemd unit.

codetrotter 2y ago

Yep. And also pay attention during package and system upgrades on some systems. In certain cases it messes up this ordering, and you end up with sshd starting before Wireguard again and then sshd doesn’t find any interface with the specified address, which in turn makes it so that it won’t bind to that address. Making the machine unreachable until you manually fix it again.

napkin 2y ago
A less finnicky approach would be binding to 0.0.0.0, then configuring incoming firewall policy. By default deny, then allow SSH through wireguard network. Or by default allow then deny SSH through public network.
- codetrotter 2y ago
  I like that idea a lot. I may start doing that.
  - semi 2y ago
    if you want to get fancy and/or over engineered you would use systemd templated units to setup sshd@.service and a ListenAddress in the config listening on %i. Then you could bring up sshd@(expectedip).service for each expected IP .. but that doesn't gain all that much tbh.if anything the only hesitation I'd have on listening to * and relying on firewall rules is if the service comes up before its configured. but exposing sshd isn't even that bad
sureglymop 2y ago
Yeah I would do it with nftables so you don't have to change the sshd listen address.
RealStickman_ 2y ago
You can create an override file for sshd to avoid issues due to package config changes. https://www.freedesktop.org/software/systemd/man/latest/systemctl.html#edit%20UNIT%E2%80%A6 https://www.freedesktop.org/software/systemd/man/latest/syst...
- codetrotter 2y ago
  I did something like that but somehow after an upgrade I still lost access to one of my systems that I had set up like that. This machine is physically in a different city from me so I rarely have the chance to go there. And lately I’ve even been in another country.

eyegor 2y ago

Why don't you just add sshd restart as an interface PostUp step in the client's wireguard config file?

kardos 2y ago
So allow sshd to start in a failed mode and then restart it?
inbetween 2y ago
it only takes 3 lines in a systemd override fille (which I think don't suffer the overwrite-on-upgrade problem). To my mind, that keeps the startup logic nicely local in service files.