summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBrian May <brian@linuxpenguins.xyz>2015-12-15 11:48:34 +1100
committerBrian May <brian@linuxpenguins.xyz>2015-12-15 11:48:34 +1100
commitce5187100c43dbf2822458a8a04e104a90d970a0 (patch)
tree0a5e9893286f8b3f3c025c67c1489ed416bacbb7
parentbdc7d3a97cb1ee56a2401051150c9f35ef2d58ad (diff)
Add to TPROXY documentation
-rw-r--r--README.rst9
1 files changed, 7 insertions, 2 deletions
diff --git a/README.rst b/README.rst
index aab1b2a..bd64a10 100644
--- a/README.rst
+++ b/README.rst
@@ -88,9 +88,14 @@ There are some things you need to consider for TPROXY to work:
Otherwise sshuttle may attempt to intercept the ssh packets, which will not
work. Use the `--exclude` parameter for this.
-4. You do need the `--method=tproxy` parameter, as above.
+4. Similarly, UDP return packets (including DNS) could get intercepted and
+ 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
+ `--exclude` parameter for this.
-5. The routes for the outgoing packets must already exist. For example, if your
+5. You do need the `--method=tproxy` parameter, as above.
+
+6. The routes for the outgoing packets must already exist. For example, if your
connection does not have IPv6 support, no IPv6 routes will exist, IPv6
packets will not be generated and sshuttle cannot intercept them::