I don't feel like this tool adds a whole lot, though an A for effort.<p><pre><code> # ~/.ssh/config
Host bastion
User user
Port 2222
Hostname my.host.com
</code></pre>
And then as a bash alias in `.bashrc`:<p><pre><code> # ~/.bashrc
alias stun='sshuttle --dns --daemon --pidfile=/tmp/sshuttle.pid -r bastion 0/0'
alias stunx='[[ -f /tmp/sshuttle.pid ]] && kill $(cat /tmp/sshuttle.pid)'
</code></pre>
Works on OSX and Linux.
This appears to be a shell script to deploy sshuttle to a DO droplet.<p>I've seen this sort of thing be helpful when the software is cumbersome to install and/or use. But, looking at the sshuttle docs, it doesn't look terribly complicated.<p>I've not used sshuttle myself, so maybe I'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://man.openbsd.org/ssh" rel="nofollow">http://man.openbsd.org/ssh</a> )<p>Why and how do you use sshutle? The doc-page for shuttle claims it's smarter than port forwarding - and I guess that might be true for some subset of protocols that isn't quite real-time (builds on udp), but yet isn't something simple like http?<p><a href="http://sshuttle.readthedocs.io/en/stable/how-it-works.html" rel="nofollow">http://sshuttle.readthedocs.io/en/stable/how-it-works.html</a>
If you have configured the host in your ~/.ssh/config then you can simply do:<p><pre><code> sshuttle -r <hostname> 0/0</code></pre>