Skip to content

Conversation

@skuhl
Copy link
Contributor

@skuhl skuhl commented Oct 21, 2020

This works for me but needs testing by others. Remember to specify a
::0/0 subnet or similar to route IPv6 through sshuttle.

I'm adding this to nft before nat since it is not sshuttle's default
method on Linux. Documentation updates may be required too.

This patch uses the ipaddress module, but that appears to be included
since Python 3.3.

This works for me but needs testing by others. Remember to specify a
::0/0 subnet or similar to route IPv6 through sshuttle.

I'm adding this to nft before nat since it is not sshuttle's default
method on Linux. Documentation updates may be required too.

This patch uses the ipaddress module, but that appears to be included
since Python 3.3.
@brianmay
Copy link
Member

Ideally some sort of automatic integration testing on these firewall methods would be really good. But I have no idea where to even start on this...

Will merge after documentation is fixed and you are happy for it to be merged.

Update docs to indicate that IPv6 is supported with the nft method.

- Adds nft into the requirements.rst file.

- Update description of what happens when a hostname is used in a
  subnet.

- Add ipfw to list of methods.

- Indicate that --auto-nets does not work with IPv6. Previously this
  was only mentioned in tproxy.rst

- Clarify that we try to use "python3" on the server before trying
  "python".
@skuhl
Copy link
Contributor Author

skuhl commented Oct 23, 2020

Ok. I think it is ready to merge!

@brianmay brianmay merged commit 5c8c707 into sshuttle:master Oct 25, 2020
@skuhl skuhl deleted the nft-ipv6 branch October 25, 2020 15:53
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