Do-Sshuttle: Transparent Proxying via DigitalOcean Droplets

I don&#x27;t feel like this tool adds a whole lot, though an A for effort.<p><pre><code> # ~&#x2F;.ssh&#x2F;config Host bastion User user Port 2222 Hostname my.host.com </code></pre> And then as a bash alias in `.bashrc`:<p><pre><code> # ~&#x2F;.bashrc alias stun=&#x27;sshuttle --dns --daemon --pidfile=&#x2F;tmp&#x2F;sshuttle.pid -r bastion 0&#x2F;0&#x27; alias stunx=&#x27;[[ -f &#x2F;tmp&#x2F;sshuttle.pid ]] &amp;&amp; kill $(cat &#x2F;tmp&#x2F;sshuttle.pid)&#x27; </code></pre> Works on OSX and Linux.

This appears to be a shell script to deploy sshuttle to a DO droplet.<p>I&#x27;ve seen this sort of thing be helpful when the software is cumbersome to install and&#x2F;or use. But, looking at the sshuttle docs, it doesn&#x27;t look terribly complicated.<p>I&#x27;ve not used sshuttle myself, so maybe I&#x27;m missing something? Is it difficult to install or use? Honestly curious what problem this shell script is addressing.

So, I too learned of sshuttle from this thread, and was wondering why anyone would want to use sshuttle over just the built-in socks5 proxy of openssh? ( -D: <a href="http:&#x2F;&#x2F;man.openbsd.org&#x2F;ssh" rel="nofollow">http:&#x2F;&#x2F;man.openbsd.org&#x2F;ssh</a> )<p>Why and how do you use sshutle? The doc-page for shuttle claims it&#x27;s smarter than port forwarding - and I guess that might be true for some subset of protocols that isn&#x27;t quite real-time (builds on udp), but yet isn&#x27;t something simple like http?<p><a href="http:&#x2F;&#x2F;sshuttle.readthedocs.io&#x2F;en&#x2F;stable&#x2F;how-it-works.html" rel="nofollow">http:&#x2F;&#x2F;sshuttle.readthedocs.io&#x2F;en&#x2F;stable&#x2F;how-it-works.html</a>

If you have configured the host in your ~&#x2F;.ssh&#x2F;config then you can simply do:<p><pre><code> sshuttle -r &lt;hostname&gt; 0&#x2F;0</code></pre>