extern/sshuttle
1
1
Fork 0
mirror of https://github.com/sshuttle/sshuttle.git synced 2025-04-21 17:58:39 +02:00
Code Issues Packages Projects Releases Wiki Activity

IPv6 routes must be added manually

Browse Source
This commit is contained in:
Brian May 2015-12-15 14:26:39 +11:00
parent ba60d22478
commit e433c599e4
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.rst
View File

@ -80,6 +80,9 @@ There are some things you need to consider for TPROXY to work:
ip -6 route add local default dev lo table 100 ip -6 route add local default dev lo table 100
ip -6 rule add fwmark 1 lookup 100 ip -6 rule add fwmark 1 lookup 100
- The --auto-nets feature does not detect IPv6 routes automatically. Add IPv6
routes manually. e.g. by adding '::/0' to the end of the command line.
- The client needs to be run as root. e.g.:: - The client needs to be run as root. e.g.::
sudo SSH_AUTH_SOCK="$SSH_AUTH_SOCK" $HOME/tree/sshuttle.tproxy/sshuttle --method=tproxy ... sudo SSH_AUTH_SOCK="$SSH_AUTH_SOCK" $HOME/tree/sshuttle.tproxy/sshuttle --method=tproxy ...
@ -90,7 +93,7 @@ There are some things you need to consider for TPROXY to work:
- Similarly, UDP return packets (including DNS) could get intercepted and - Similarly, UDP return packets (including DNS) could get intercepted and
bounced back. This is the case if you have a broad subnet such as bounced back. This is the case if you have a broad subnet such as
``0.0.0.0/0`` that includes the IP address of the client. Use the ``0.0.0.0/0`` or ``::/0`` that includes the IP address of the client. Use the
`--exclude` parameter for this. `--exclude` parameter for this.
- You do need the `--method=tproxy` parameter, as above. - You do need the `--method=tproxy` parameter, as above.