[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 lpirl):

 Replying to [comment:33 warner]:
 > 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.

 Although I am not sure to what extend we're willing to change the
 semantics of the config file but it's an option to rename `tcp:` to
 `tcp4:`, introduce `tcp6:` and use `tcp:` for trying IPv4 and IPv6.
 IMHO, most people probably don't care with which IP version data is
 carried.
 For those who do, there is the flexibility to configure it.

 > 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.

 Well, staying with the semantics above, `tcp:` (or any other auto-detected
 thing) could fail silently if at least one IP version works.
 Explicit configurations should fail loudly.

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