Skip to content

Conversation

@skuhl
Copy link
Contributor

@skuhl skuhl commented Dec 29, 2020

If you use the tproxy method with a large subnet (such as 0/0), then (1) you may not receive UDP packets that sshuttle/tproxy can handle and (2) you are unable to connect (i.e., ssh) to your machine using an IP that your computer recognizes as its own.

To resolve those issues, any traffic to an IP that the host knows is local, does not go through the sshuttle chains.

If you use the tproxy method with a large subnet (such as 0/0), then
(1) you may not receive UDP packets that sshuttle/tproxy can handle
and (2) you are unable to connect to your machine using an IP that
your computer recognizes as its own.

To resolve those issues, any traffic to an IP that the host knows is
local, does not go through the sshuttle chains.
@brianmay brianmay merged commit 97c25e9 into sshuttle:master Jan 3, 2021
@skuhl skuhl deleted the tproxy-local-fix branch March 9, 2021 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants