Dynamic port forwarding using SSH, SOCKS5 and a VPS

I recommend using &quot;autossh&quot; to maintain ssh tunnels, since they could be flacky on some connections.<p>One day I should do a write up, but i have made an interesting setup for some robots I made<p>Server (with bots) &gt; ssh tunnel maintained by autossh &gt; vps &gt; tinyproxy listening to localip and binded to open vpn connection &gt; sending traffic on via an openVPN connection to random server (purevpn) in US<p>I even made scripts to periodically check status of the remote vpn status on the vps and reconnect if they went down<p>tl.dr:<p>Server &gt; VPS with tinyproxy&#x2F;openvpn &gt; VPN Provider ips &gt; Internet<p>I could probably do it all on same server but its handy being able to switch off the vps (and hence not pay for resources) when not in use and keeping things separate

I&#x27;m sorry, but what&#x27;s the point of this? Most of it is basic linux ssh setup, and the rest is running<p><pre><code> ssh -D 8080 </code></pre> Most of the setup isn&#x27;t even required. SSH forwarding works out-of-the box for the vps provider I&#x27;m using.

I Just use foxyproxy in Firefox or Chrome for fast proxy switching, good write up overall, never heard of &quot;ufw&quot; iptables friendlier frontend script, I will try it out.

ssh -D is half the story of the problem, particularly with socks5a DNS over it.<p>I&#x27;m becoming a bigger fan of sshuttle, everytime I need to use it.<p>Mostly by running SSH over the proxies using a CONNECT string (corkscrew) or using a ssh proxy-command to hop once over out of a DMZ.<p>Those combinations &amp; composability of ssh is what makes it so much more useful inside a limited network.

Instead of this wall of text I use Viscosity+pritunl vpn on gce. 5-clicks setup and works fine.