IPv6 bootstrappers and websites

[victorb]

Right now, Bootstrap nodes only run IPv4. We would like to enable IPv6 to have better discoverability and connectivity.

• Figure out what we have to do to enable IPv6 and setup following actions

[ghost]

notes from #88

• enable ipv6 for each droplet in an older datacenter
• programatically set ip addresses on hosts (i.e. /etc/network/interfaces et. al.)
• give ipfs container an address from the /64 (https://docs.docker.com/engine/userguide/networking/default_network/ipv6/) not neccessary, ipfs container use the host network stack
• swarm listens on /ip6/::/tcp/4001
• /ip6 addrs in default bootstrap list of go-ipfs and js-ipfs

and for the gateway:

• nginx listens on /ip6/::/tcp/80 and /ip6/::/tcp/443
• AAAA records for ipfs.io, gateway.ipfs.io
• AAAA records for websites like ipld.io

[ghost]

ipfs.io, gateway.ipfs.io, as well as the default bootstrappers do now speak IPv6, and there's been a nice bump in the number of IPv6 peerings:

Note: I restarted all these nodes to trick their peers into retrying, and possibly using /ip6 this time.

Left to do:

• /ip6 addresses in the default bootstrap list of go-ipfs and js-ipfs
• DNS records for websites other than ipfs.io

[victorb]

Missing merged into go-ipfs to start using IPv6

[ghost]

add /ip6 bootstrap config

• go-ipfs: bootstrap: add a few /ip6 nodes kubo#3523
• js-ipfs: Add /ip6 addresses to bootstrap js-ipfs#706