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

tahoe-lafs trac at tahoe-lafs.org
Mon Mar 4 12:35:47 UTC 2013


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

Comment (by gdt):

 A few comments:
  * the URL of your git repo/branch should probably be in this ticket
  * Probably someone (you?) should file a separate ticket for making the
 WUI listen on ::1 (and presumably then the CLI interface could use that
 next, another ticket).
  * whether a node is willing to use v4 vs v6 for outgoing connections
 should be separate from whether the node listens on v4 or v6 (foolscap)
  * the concept of the port file seems a little off.   nodes listen on an
 address/port pair, or rather a set of them.  what port means now is "put
 this together with INADDR_ANY".  But, it could be "put it with INADDR_ANY,
 and also with INADDR6_ANY".   So probably the node config needs a config
 to list the address families on which to listen, defaulting to all OS-
 supported families.  (For extra credit, test on a BSD system without INET
 in the kernel - I need to see if that still builds, and if not fix it.)  I
 suggest "IncomingFamiles = inet6, inet", being a set.
  * for outgoing connections, the introducer furl, or data from the
 introducer, will have a list of addresses.  I think it makes sense to 1)
 include a list of acceptable address families, defaulting to all OS-
 supported families and 2) have a way to express preference.  For
 preference, I would start with v6, following the modern tradition.   So I
 can see this being a "OutgoingFamilies = inet6, inet" and it being a list
 rather than a set.

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


More information about the tahoe-lafs-trac-stream mailing list