2 ms·
AutoSSH and port forwarding. You can even forward points behind a NAT. I use this technique to get to “my” box on “your” network, no firewall config changes,
by randombits0 5y ago
AutoSSH and port forwarding. You can even forward points behind a NAT. I use this technique to get to “my” box on “your” network, no firewall config changes, no issues, it “just works”.
Now I’ve never tested this with a public/high(er) volume service but it lets me pen test internal networks just like I’m sitting in the NOC. And my “VPS” host can handle dozens of simultaneous connections to dozens of endpoints. I have SSH listening on a non-standard port (eliminates 95% of the script-kiddie noise) and cert auth. That’s the only listening service on the VPS box.
I am familiar with some “TCP-in-TCP” problems but I’ve never had any. If it falls down, it just reconnects when traffic can pass again.
So what am I missing?
- creeble 5y agoI use this technique as well, and don’t understand enough about wireguard to know why it would be better. AutoSSH has been 100% reliable for me, with any lost connection restarting without conflicts, duplication, or error. My AT&T connection is definitely not five nines, so any tunnel needs to deal with restarts very well.