Opened at 2009-12-20T22:17:06Z
Last modified at 2020-01-18T00:22:19Z
#867 closed enhancement
use ipv6 — at Initial Version
Reported by: | warner | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | code-network | Version: | 1.5.0 |
Keywords: | ipv6 firewall twisted foolscap test-needed | Cc: | clashthebunny@…, mmoya@…, zooko, tahoe-lafs.org@… |
Launchpad Bug: |
Description
Shawn Willden points out that IPv6 is a likely way to deal with the servers-behind-NAT problem (#169, #445, #49, #50), since a lot of ISPs offer v6 tunnel services these days, which effectively gives the server host a publically-reachable v6 address.
To make this work, we need a couple of things, probably in the following order:
- python must handle v6 addresses, in the socket module
- twisted must handle v6 addresses: connecting to them, reporting them when asking a socket who it is connected to, and enumerating them on listenable interfaces. The existing IPv4Address class must grow a corresponding IPv6Address partner.
- foolscap must handle them: putting them in connection hints (foolscap#60 has some notes on formats), connecting to them, etc
- tahoe must handle them: formatting them into Welcome page listings, passing them through the Introducer without problems, logging them correctly
Let's collect pointers to other tickets (especially the twisted ones) and progress reports here.
Note: See
TracTickets for help on using
tickets.