This. Using simple ssh tunneling with port forwarding in a similar scenario. Working flawlessly with zero maintenance for 5 years and counting. Very reliable
Comment on Best way to get IPv4 connectivity to my self-hosted services
Shimitar@downonthestreet.eu 2 days ago
Wire guard to the vps with nftables port forwarding.
Check my wiki here wiki.gardiol.org/doku.php?id=networking%3Awiregua…
Or setup ssh with port forwarding as well. Less reliable but nothing to install on a basic Linux.
ari_verse@lemmy.ca 2 days ago
Shimitar@downonthestreet.eu 2 days ago
Not really reliable, much less than wire guard. If your connection is unstable ssh not the best option. Autossh make it better, but still after a forced disconnection ssh will take a while to drop and reconnect. Wire guard is much better. I moved from ssh+autossh to wireguard and wished I did that sooner.
ari_verse@lemmy.ca 2 days ago
Fair comment, I should qualified my answer: I use an ssh tunnel with auto-reconnect option, wrapped inside a systemd service. In all this years, I still have to run into a problem that wasn’t external (server down, no internet at home etc) I agree that wireguard is the proper solution however it requires a lot of extra configuration and support in both ends, which now is prevalent but not so much 5+ years ago. Also for a single port solution, ssh is so much simpler, practical and reliable, you only need an ssh user at the other end.
ExecStart=/usr/bin/ssh -NT -o ServerAliveInterval=60 -o ServerAliveCountMax=3 -o ExitOnForwardFailure=yes -R localhost:YOUR_PORT:localhost:YOUR_PORT SOME_USER@YOUR_SERVER\
DevoidWisdom@sh.itjust.works 1 day ago
I do this already, but I’m going compare my nftables rules when i get home. You’re ip table looks more elegant.