The key difference is you can right full or partial traffic (by subnet) over SSH with applications not being aware - individual applications do not require SOCKS support.
Route* not right. As an example, you can send traffic destined for 142.0.0.0/8 via the SSH connection, and leave everything else untouched. Any application connecting to that IP range will be automatically tunnelled via SSH.
Comments
Isn’t this just recreating the existing functionality you can get with a Socks proxy and stock ash?
"sshuttle assembles the TCP stream locally, multiplexes it statefully over an ssh session, and disassembles it back into packets at the other end."
Source:
https://sshuttle.readthedocs.io/en/stable/how-it-works.html
The key difference is you can right full or partial traffic (by subnet) over SSH with applications not being aware - individual applications do not require SOCKS support.
Route* not right. As an example, you can send traffic destined for 142.0.0.0/8 via the SSH connection, and leave everything else untouched. Any application connecting to that IP range will be automatically tunnelled via SSH.
Ahh, gotcha. That is indeed a neat feature.