13 ms·
Enabling IPv6 support for GitHub Pages
- an_d_rew 5y agoThank you! I know it’s all the rage to say “gee why no v6 yet?”, but that’s a LOT of infrastructure and testing to overhaul… The effort is much appreciated!
- trevcanhuman 5y agoI don’t really understand the benefits, would you mind explaining them to me ?
- metalliqaz 5y agothe Internet is almost out of IPv4 addresses, and the ones that are left are becoming expensive to obtain. Rather than hide whole blocks of users behind NAT, they can just use IPv6.
- voiper1 5y ago>Rather than hide whole blocks of users behind NAT, ... which creates all sorts of routing issues. If you don't have your own publicly accessible IP address it creates all sorts of connection issues.
- metalliqaz 5y agofor some use cases. for example, most home users are behind ipv4 NAT because of their wifi routers. nobody really notices a problem.
- Plasmoid 5y agoMostly because we've invested huge amounts of engineering effort to work around the problems. The result is that for the most common use cases, things mostly work. NAT systems are optimized for a few devices to be active at a time. As the number grows they might not co-operate well. Game consoles are infamous for networking problems when you have anything other than a single machine.
- iggldiggl 5y agoAnd the Wifi router is at least under my control (although depending on where you live and which ISP you use even that isn't necessarily true), so I can still set up some port forwarding for my internal devices as required. Because of the shortage of IPv4 addresses however carrier-grade NAT is becoming more and more common, which is truly an abomination.
- dx034 5y agoI don't want to have my own IP, at least not without frequent changes. My servers should have static IPs but having static IPs at home or for mobile devices only makes tracking easier..
- throw0101a 5y ago> I don’t really understand the benefits, would you mind explaining them to me ? Want to run a public service with end-to-end connectivity? Go to your RIR to request an IPv4 block and be put on a waiting list. Or break out your cheque book and be prepared to cough up $35+/IP for the privilege: * https://auctions.ipv4.global https://auctions.ipv4.global * https://ipv4marketgroup.com/ipv4-pricing/ https://ipv4marketgroup.com/ipv4-pricing/ * https://ipv4connect.com/marketplace https://ipv4connect.com/marketplace Or get an IPv6 address block right away for $0.
- commandersaki 5y agoYou'd still need IPv4 to connect with the Internet.
- MayeulC 5y agoWith the IPv4 internet, that is. You don't need IPv4 to connect to most GitHub pages anymore. Admittedly, IPv4 internet is a good chunk of the Internet, but maybe not the part of interest to you at a given point in time. http://www.delong.com/ipv6_alexa500.html http://www.delong.com/ipv6_alexa500.html
- throw0101a 5y agoPlenty of folks are IPv6-only. Mobile on T-Mobile for example: * https://www.youtube.com/watch?v=nNMNglk_CvE https://www.youtube.com/watch?v=nNMNglk_CvE
- MayeulC 5y agoIPv6-only hosts will be able to connect to github pages now, if configured properly. There are a couple use-cases for that, but it should allow cheaper VPSes, or less complicated network configuration by eliminating NAT. If a host only needs to access GitGub and a few select hosts, it can be granted an IPv6 without setting up DHCP, NAT, IPv4 routing tables, etc. I've been considering using NAT64 as a way to eliminate the need for dedicated IPv4 configuration at home, unfortunately I recently moved, and the current provider is IPv4-only. This infuriates me to no end.
- deleted 5y ago[deleted]
- azernik 5y agoThe big one is the address space expansion, which in addition to solving "can't get addresses" also makes routing cheaper and faster (can allocate addresses based on network topology, rather than on what's available). Whole they were breaking backwards compatibility anyway, they also introduced a faster way of getting initial addresses, changed headers and dropped some features to make routing easier to implement in hardware, and added some features to make annotation of packets in the network backbone during transit easier.
- curiousmindz 5y agoIt boggles my mind that IPv6 has such a slow roll out (it's been a thing since the early 2000s = twenty years ago). I would have thought that all the major tech companies supported it years ago on all their infrastructures, websites and apps. But there are still a lot of hold outs. What about IPv6 makes it such a chore to become widespread?
- zokier 5y agoI think its more of a matter of perception than anything. IPv6 adoption has gone pretty smoothly imho, there hasn't been any major blowbacks or anything; for example the Google IPv6 adoption chart trend is steadily increasing. Another thing you can see from Google IPv6 charts that before 2011 IPv6 adoption was near zero. This matches pretty well with IPv4 exhaustion; IANA pool was exhausted in 2011, and APNIC followed later that year. Before that anyone could get IPv4 address pretty liberally, so there was very little reason to think about IPv6. Especially in western world (RIPE/ARIN) where consumption was slower than e.g. APNIC; notably ARIN reached exhaustion only in 2015. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html In summary, I feel that having third of internet become ipv6 in about a decade seems pretty decent result, considering how complex and especially diverse internet is.
- xxpor 5y agoSomeone pointed out recently on NANOG the thing that probably killed a TON of IPv6 momentum was when they missed the deadline to get it included in Windows 95. Approximately no one was on the internet before then. (Yes yes you nerds were, but most people weren't)
- zokier 5y agoSeems pretty far fetched to me that there would have ever been a chance to have IPv6 in Win9x. For comparison, afain FreeBSD was the forerunner with IPv6 support, and they got it in 2000. So I'd say they "missed the deadline" by 5+ years. It was probably around 2005 when we realistically had somewhat usable IPv6 support at base OS level.
- pdmccormick 5y agoThat is a pleasantly concise announcement.
- kaliszad 5y agoWe have created perhaps an easier documentation on how to make it all work on your own domain, with many screenshots and such. Here it is: https://www.orgpad.com/s/cjzpkTRIK_L https://www.orgpad.com/s/cjzpkTRIK_L
- zokier 5y agoOne interesting observation about IPv6 I've made is that in Europe IPv6 and FTTx seem inversely correlated. For example Spain is one of the leaders in FTTx with 87% of homes covered, but have only 3% IPv6 adoption according to Google. Meanwhile Germany has one of the highest IPv6 adoptions in Europe, 52%, and one of the lowest FTTx coverages (16%). Latvia, Lithuania, Belarus, and Iceland all have 90% FTTx and 10% IPv6. UK, Finland, Belgium, and Netherlands on the other hand seem to be having better IPv6 adoption than FTTx. My guess is that ISPs must have needed to choose if to invest to core network or to last mile, and that is visible here. But at the same time it seems bit weird that you'd in 2020s deploy fancy new fiber networks without IPv6.
- deleted 5y ago[deleted]
- commandersaki 5y ago> My guess is that ISPs must have needed to choose if to invest to core network or to last mile, and that is visible here. But at the same time it seems bit weird that you'd in 2020s deploy fancy new fiber networks without IPv6. Well there's no real value connecting to an IPv6 island. The Internet is still IPv4.
- ce4 5y agoI wouldn't count it like that. Germany's top provider Deutsche Telekom has a market share of around 40% and has enabled IPv6. Vodafone as well.
- deleted 5y ago[deleted]
- kmp3e 5y agoTook way too long for this to happen
- runxel 5y agoOfftopic, but still relevant: Github pages could also use to get a newer Jekyll version...
- floatboth 5y agoNow how about GitHub itself?