[tahoe-lafs-trac-stream] [Tahoe-LAFS] #867: use ipv6

[Tahoe-LAFS]

#867: use ipv6
-------------------------+-------------------------------------------------
     Reporter:  warner   |      Owner:  ClashTheBunny
         Type:           |     Status:  assigned
  enhancement            |
     Priority:  major    |  Milestone:  undecided
    Component:  code-    |    Version:  1.5.0
  network                |   Keywords:  ipv6 firewall twisted foolscap
   Resolution:           |  test-needed
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 Oh, actually, this might need more work. I'm doing some manual testing,
 and it looks like our default behavior of listening on `tcp:PORT` only
 makes an IPv4 listening socket. I tried connecting to that (on a host with
 both IPv4 and IPv6 addresses bound to en0) with `nc -6 IPV6ADDR PORT` and
 it wouldn't connect. If I listen on `tcp6:PORT` then `nc -6` works but `nc
 -4` doesn't.

 I think we might need to listen on both `tcp:PORT` and `tcp6:PORT` to
 allow A+AAAA hosts to accept both v4 and v6 connections.

 If so, we need tahoe.cfg's `tub.port=` to accept multiple ports (or
 second-guess the user and automatically add `tcp6:` every time we see
 `tcp:`, which feels a bit wrong). We either need a delimiter (whitespace?
 comma?) or to accept multiple config keys (like `tub.1.port=` and
 `tub.2.port=` or something). And we need the default create-node behavior
 to produce both kinds.

 And we need to see what happens if you try to listen on `tcp6:1234` on a
 box that doesn't have IPv6 support: either catch+ignore the error, or test
 ahead of time and avoid it.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/867#comment:33>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage