Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
S
sshuttle
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
pub
sshuttle
Commits
e433c599
Commit
e433c599
authored
Dec 15, 2015
by
Brian May
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
IPv6 routes must be added manually
parent
ba60d224
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
1 deletion
+4
-1
README.rst
README.rst
+4
-1
No files found.
README.rst
View file @
e433c599
...
@@ -80,6 +80,9 @@ There are some things you need to consider for TPROXY to work:
...
@@ -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:
...
@@ -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.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment