|
2012-04-03
, 21:26
|
Posts: 1,141 |
Thanked: 781 times |
Joined on Dec 2009
@ Magical Unicorn Land
|
#2
|
The Following User Says Thank You to stlpaul For This Useful Post: | ||
|
2012-04-03
, 23:20
|
Posts: 346 |
Thanked: 271 times |
Joined on Jan 2010
|
#3
|
|
2012-04-04
, 11:07
|
Posts: 346 |
Thanked: 271 times |
Joined on Jan 2010
|
#4
|
|
2017-04-18
, 11:37
|
Posts: 7 |
Thanked: 1 time |
Joined on Apr 2017
@ Pune
|
#5
|
|
2017-09-20
, 07:28
|
Posts: 2 |
Thanked: 0 times |
Joined on Sep 2017
@ India
|
#6
|
Pretty neat for the N900 considering how inconvenient it is to change socks or proxy settings.
Project homepage: https://github.com/apenwarr/sshuttle
NEWS: Version 0.50a adds support for DNS proxying (new --dns switch). So now both TCP packets and DNS requests are sent over the tunnel
Requirements:
Path for git core files is not set correctly. You need to add it to your path. See thread here http://talk.maemo.org/showthread.php...git+index-pack
sshuttle can now auto-detect that the "-m ttl" stuff doesn't work, and try again without it in that case.
First you need to be root.
You can now use all the applications dealing with TCP protocol (web browser, command line...). With the new --dns switch DNS requests are also sent through the SSH tunnel.
There is also a new switch on 0.50a for addressing latency issues.
--no-latency-control: disable the "check_fullness" feature that
prevents a bandwidth-intensive sshuttle channel, like a huge rsync,
from killing the latency of other channels. If your network is very
fast but has high latency, the latency control prevented you from
using all your bandwidth, and sometimes you just don't care about
latency.
TIPS1: RSA keys and alternate ports
For that you either need to use sshagent or a /root/.ssh/config file. Here is how to do it with a SSH config file:
Latest version of sshuttle now autodetects installed Python versions and adjust its settings to select the Python interpreter (i.e. ArchLinux).
Last edited by alphazo; 2011-02-09 at 09:11.