Status of IPv6 support in Openstreetmap
There is an openstreetmap tile server for the Netherlands running over IPv6, and another one in France with worldwide coverage (including for HOT projects).
But at the current time, most of the default OpenStreetMap servers do not run over IPv6, and are not even reachable directly by IPv6-only clients (which must then use third-party proxies or establish IPv6-to-IPv4 tunnels, whose web sessions are frequently very limited in terms of privacy, response time, duration, volume, bandwidth, reliability and quality of service). This is now becoming a problem for many users, notably those connected on mobile networks.
|Hostname||AAAA DNS record||IPv6 web server||IPv6 DNS server||As of date||Note|
|osm.org||yes||yes||yes||2017-11-26||Short alias of openstreetmap.org|
|api.openstreetmap.org||yes||yes||yes||2017-11-26||Main API for data submission (for editors) and queries|
|lists.openstreetmap.org||yes||yes||yes||2017-11-26||Mailing lists online subscription and archives|
|a.tile.openstreetmap.org||no||?||?||2017-11-26||Default layer on main site, CDN|
|forum.openstreetmap.org||no||?||?||2017-11-26||Used by main site|
|piwik.openstreetmap.org||no||?||?||2017-11-26||Used by main site|
|stateofthemap.org||no||?||?||2017-11-26||State of the Map (SotM) international conference|
|a.tile.thunderforest.com||no||?||?||2017-11-26||Cycle maps, Public transport layers|
|a.tile.openstreetmap.fr||yes||yes||yes||2017-11-26||Humanitarian OSM Team, and some other layers|
|Other OSM-related servers|
|overpass-turbo.eu||yes||yes||no||2017-11-26||Overpass Turbo, depending on overpass-api.de (by default)|
|overpass-api.de||yes||yes||yes||2017-11-26||used by e.g. overpass-turbo.eu|
|overpass.openstreetmap.fr||yes||yes||yes||2017-11-26||used by e.g. overpass-turbo.eu|
|overpass.osm.rambler.ru||no||?||?||2017-11-26||used by e.g. overpass-turbo.eu|
|osmose.openstreetmap.fr||no||?||?||2017-11-26||Osmose quality assurance tool|
This can be tested on http://ipv6-test.com/validate.php
It has been tested that an AYIYA tunnel from SixXS works from UCL; this basically says that we can make a tunnel from UCL to a nearby tic server in London. The setup time for that is the time to apply at SixXS and the time to request a tunnel. From that point on a subnet can be requested that is (on layer 2) distributing IPv6 using radvd automatically. No setup required, only a IPv6 module loaded in the respectable kernel.
Most likely because we have static ip adresses, we don't want to tunnel over AYIYA out, but directly get a static IPv4 link, without heartbeat. We did not test that yet, but if tested and it works within UCL it would be the best method.
Obviously IPv6 makes machines directly accessible like global IPs do. By putting a firewall on top of the router that is distributing the IPv6 adresses, we basically protect us against people trying to reach the machines by v6. Setting up again a port based match is transparent to IPv4 and IPv6; so theoretically if every system has a firewall now, it would already be protected.