Skip to content

Commit 1e04eb1

Browse files
committed
Updates to TPROXY docs.
1 parent 117afc7 commit 1e04eb1

File tree

1 file changed

+14
-5
lines changed

1 file changed

+14
-5
lines changed

README.rst

Lines changed: 14 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -84,13 +84,22 @@ There are some things you need to consider for TPROXY to work:
8484

8585
sudo SSH_AUTH_SOCK="$SSH_AUTH_SOCK" $HOME/tree/sshuttle.tproxy/sshuttle --method=tproxy ...
8686

87-
3. You do need the `--method=tproxy` parameter, as above.
87+
3. You may need to exclude the IP address of the server you are connecting to.
88+
Otherwise sshuttle may attempt to intercept the ssh packets, which will not
89+
work. Use the `--exclude` parameter for this.
8890

89-
4. The routes for the outgoing packets must already exist. For example, if your
91+
4. You do need the `--method=tproxy` parameter, as above.
92+
93+
5. The routes for the outgoing packets must already exist. For example, if your
9094
connection does not have IPv6 support, no IPv6 routes will exist, IPv6
91-
packets will not be generated and sshuttle cannot intercept them. Add some
92-
dummy routes to external interfaces. Make sure they get removed however
93-
after sshuttle exits.
95+
packets will not be generated and sshuttle cannot intercept them::
96+
97+
telnet -6 www.google.com 80
98+
Trying 2404:6800:4001:805::1010...
99+
telnet: Unable to connect to remote host: Network is unreachable
100+
101+
Add some dummy routes to external interfaces. Make sure they get removed
102+
however after sshuttle exits.
94103

95104

96105
Obtaining sshuttle

0 commit comments

Comments
 (0)