GitHub Community
Replies: 150 comments 358 replies
-
|
I am unable to understand what in 2022 still holds full IPv6 support for a platform like GitHub. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
https://www.githubstatus.com/incidents/5y8b8lsqbbyq
looks like they are preparing for IPV6 |
Beta Was this translation helpful? Give feedback.
-
At OtherBigCompany, the networking libraries would convert IPv4-mapped addresses to plain IPv4 immediately after reading from the socket, to avoid this class of problem. Ideally nobody should see an |
Beta Was this translation helpful? Give feedback.
-
|
yes of course |
Beta Was this translation helpful? Give feedback.
-
|
Yes that's true |
Beta Was this translation helpful? Give feedback.
-
|
New ISPs in my country are IPv6-only because there is no new IPv4 space to be provided to them. They do have a over-shared IPv4 address by CGNAT but due to the oversharing, it is unstable and not rare to be offline. For these companies, the internet access is stable only in IPv6. Thinking about the server-side, some cloud providers are making extra charges for IPv4 addresses (e.g.: Vultr.com) so most of the servers in my company are IPv6-only. Cloning github repositories is very cumbersome due to the lack of IPv6 support and this issue affects me and my team mates on a daily basis. The math is simple: there are 4.88 billion internet users in the world but the IPv4 space only provides 4 billion addresses. It's over: IPv4 is obsolete and is provided in a legacy mode. Current applications and services must be IPv6 enabled otherwise it should be seen as obsolete. For that matter, Github.com is an obsolete service because it relies on obsolete technology as IPv4. |
Beta Was this translation helpful? Give feedback.
-
|
That's exactly what I keep telling people. There are companies in developing countries that will not be able to afford the high markup price on IPv4 addresses. It's a shame how little this industry actually cares about progress and standards. Makes me furious sometimes. |
Beta Was this translation helpful? Give feedback.
-
|
They'd need a NAT64 gateway to reach github not a tunnel as they already have native IPv6. |
Beta Was this translation helpful? Give feedback.
-
|
what country is that? |
Beta Was this translation helpful? Give feedback.
-
|
@divinity76 Brazil |
Beta Was this translation helpful? Give feedback.
-
|
In a CGNAT scenario, it is easy to trigger a limit rate based on ip authentication. |
Beta Was this translation helpful? Give feedback.
-
|
I really tried to use github in a IPv6 Only Network and I was not successful. Is there any plan on the github's roadmap to fully adopt IPv6? |
Beta Was this translation helpful? Give feedback.
-
|
If GitHub can't get v6 on GitHub.com soon, maybe at least an ipv6.github.com proxy for SSH git cloning? |
Beta Was this translation helpful? Give feedback.
-
|
IPv6 is the actual internet protocol, while IPv4 is a legacy protocol. Please, priorize this request. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
GitHub SSH is probably a custom implementation, and even if not the authentication and logging, as well as all tools that is reading and searching in those tools needs to be tested. I think there is no excuse to not have IPv6, but at the same time I atleast understand that it is not just a "frontend reconfiguration" |
Beta Was this translation helpful? Give feedback.
-
|
Please try it, I still think that they have issues with client IPs in logging that is causing the major delays. |
Beta Was this translation helpful? Give feedback.
-
|
@aparcar in the end I decided to remove my messages because I was not very keen to reply to the non-sense. |
Beta Was this translation helpful? Give feedback.
-
A load balancer is at its core just an http proxy. There's no reason it can't listen on ipv6 and make requests to ipv4 backend hosts. |
Beta Was this translation helpful? Give feedback.
-
Not all load balancers work at the HTTP(S) level. Although it is probably true that whatever load balancer used could be made to work with IPv6.
There are solutions to this problem, but one problem is logging and abuse detection. I think it's likely that some methods currently in place rely on IPv4. Of course that doesn't mean it's not possible to adapt to IPv6 as well, but not necessarily trivial. |
Beta Was this translation helpful? Give feedback.
-
|
My private ci is forced to go full IPv6 only, and this requires me to have one IPv4 gateway to access github. This in turn means I keep running into rate limits all the time. For now I've worked around this with an access token, but that's not sustainable. Any ipv6 support would be much appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
Is GitHub deprecated or why there is still no IPv6 support? We are talking about a over 20 year old technology and the standard for about 5 years. |
Beta Was this translation helpful? Give feedback.
-
|
No, no. It's apparently just more important to rename the "master" branch to "main". |
Beta Was this translation helpful? Give feedback.
-
|
@MrLawrence no truer words have been spoken. What an absolute joke |
Beta Was this translation helpful? Give feedback.
-
|
Probably because people that manage the technical team still didn't realize what this mean and didn't prioritize it enough. Well, then why hasn't all that been done beforehand and being carried out gradually that we can some progress on it ? Are there people working dedicated to make that happen ? After companies like Google, Facebook, Netflix, Akamai, Cloudflare have made it 100% I don't see any other strong arguments for companies use complexity as a reason to delay it further. Hope someone from GitHub's team is reading it. |
Beta Was this translation helpful? Give feedback.
-
|
It's kind of weird because RFC1883 was published in the final decade of the 1900s, over a quarter of a century ago. That was long before git was invented; let alone GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree! Defined as current in RFC8200 |
Beta Was this translation helpful? Give feedback.
-
|
Imho IPv6 is a lot easier than IPv4. Also it's not that big difference from IPv4. Big companies just lazy on setting it up. It's just a shame to see services still not available with IPv6. |
Beta Was this translation helpful? Give feedback.
-
|
I vaguely remember that years ago (pre-MS, pre-pandemic) somewhere Github engineers held a talk (or maybe it was a blog posting?) which more less said that IPv6 is in the makes, but less trivial than one might think. I just can't find that talk or slides or so anymore. I also vaguely remember that they mentioned What I though have found is that there is an ipv6 label in Github's blog — it though only lists one posting so far, which talks about Github Pages now having IPv6 support. There even once was But yeah, another Github user here with (on purpose) trying to run hosts IPv6 only and the first (and so far only) hard stumbling block was not being able to clone Git repos from Github. 🤌 I wonder if I should use Gitlab.com for these repos, because they do have an AAAA record for their main site: |
Beta Was this translation helpful? Give feedback.
-
|
It's 2022, World IPv6 Launch Day was 10 years ago. Yet, GitHub still doesn't have IPv6 support. The IPv4 address space is exhausted for years now, and ISPs are using techniques such as CGNAT to still be able to give their customers access to the legacy IPv4 internet, with the instability of these techniques as the cost. Why doesn't GitHub provide native IPv6 support? And, more importantly, is IPv6 support for GitHub on the roadmap? |
Beta Was this translation helpful? Give feedback.
-
|
Biggest fail i ever saw. |
Beta Was this translation helpful? Give feedback.
-
|
CC rust-lang/cargo#10711 this causes real issues for open source software users. This is an absurd conversation in 2022. |
Beta Was this translation helpful? Give feedback.
-
|
Try 2024... What's the over/under on Github having IPv6 support in 2026? Also, WTF, github? I'm guessing all the greybeards who actually built the thing are long gone and the generation that is there can barely touch anything without something breaking. Ever hear of "code smell"? Not supporting IPv6 in 2024 as the premier developer SCM website is a massive "org smell" |
Beta Was this translation helpful? Give feedback.
-
|
This is $MS. This company was and will be ever a enemy of open source or new technologies that comes not from $MS. They did nothing that helps the community. $MS is only interested in earning money and gives a shit on your needs |
Beta Was this translation helpful? Give feedback.
-
|
How can you not have ipv6? Some cloud providers charge extra for ipv4! |
Beta Was this translation helpful? Give feedback.
-
|
I ran into this with Hetzner last week and I'm still on the journey to get IPv6 working across all my internets. And then I run into this Github stupidity. Unbelievable. |
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
Would any Github/Microsoft representative tell us in which year, century or millenium will they support IPV6? We have public cloud environments where we are with IPV6 only already... Although, based on recent experience with Azure, I think their public cloud environment is also like with 10 years behind Google and Amazon's public cloud anyway. Why would they bother for Github? |
Beta Was this translation helpful? Give feedback.
-
|
An „effort“ you 1000% need because officially IPv4 is considered deprecated (legacy) and the current protocol of the world wide internet (yes, there’s internet outside of the freakin USA) is IPv6. The only „valid“ reason is that they want to milk the users happily paying for IPv4 as long as they can. Remember: Even freakin Governments (which are officially the slowest entity of the universe) have successfully implemented IPv6 years ago - and yet GitHub claims to be „tech savvy“ - pure comedy 🤣🤣🤣Am 25.07.2024 um 23:49 schrieb Tony Metzidis ***@***.***>:
Is there any valid excuse
you are trivializing the issue . ipv6 is a separate stack and a significant effort. at a company like github at least 3-5 engineers + support staff for a few months
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
you are trivializing the issue If I'm able to do that with a dozen virtual machines in an evening, for sure Github (or the owner Microsoft which proudly implemented IPv6 with Windows XP!) should be able to manage that within a quarter of a century. Excluding by definition half of the humans on earth (No of human beings - number of available IPv4 addresses) doesn't seem reasonable for a leading tech company. |
Beta Was this translation helpful? Give feedback.
-
|
what's going on here unsubscribe |
Beta Was this translation helpful? Give feedback.
-
|
Same thing that's been going on for years. People stating lots of reasonable reasons why Github should be reachable over IPv6, and Github just ignoring everything staying on Legacy IP. |
Beta Was this translation helpful? Give feedback.
-
|
And some people be like
"iT Is nOt eAsy yOU kNow" |
Beta Was this translation helpful? Give feedback.
-
|
IPv4 is officially a „legacy“ protocol - we no longer use token-ring, do we? Legacy is another word for DEPRECATED which is another word for „old stuff that needs to fade out“. Every new webservice should ditch IPv4 and go v6-only - it’s the new world and only IPv6 allows ALL People on this globe to access resources.It’s finally time for GitHub to put on the adult pants and accept that you NEED IPv6 - it is the freakin standard - there’s not even a discussion, it’s a damn FACT! It’s really shameful that GitHub straight refuses to use IPv6 - it really shows their lack of technical expertise… Devs depend on GitHub and therefore they have a responsibility to deploy it (they had at least 10+ years)…Am 26.07.2024 um 16:11 schrieb Al Sutton ***@***.***>:
For over 10 years, "Internet" now means IPv6
No it doesn't.
IPv6 and IPv4 are both "Internet Protocols". That's literally what the "IP" part stands for. The "Internet" is the superset of machines which communicate using one, or both, protocols. Not supporting both does not mean something isn't available on the "Internet". That's like trying to change the definition of a house and then saying that all houses that weren't built in a way you like can't be called houses any more.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
No, it doesn't. Look at the Google data posted earlier in the thread. Less than 50% of the internet has adopted IPv6, and there are several IPv4-only ISPs (e.g. PlusNet in the UK, 750k users), where people would face the inverse problem that folk accessing GH have; IPv4 only client, IPv6 only host, no access. Ditching IPv4 would cut off over 50% of Internet users, and that would be a really bad decision for any business that currently can be accessed by a number far higher than 50% of Internet users (probably 80/90%+)
You may consider it legacy, deprecated, decrepit, or whatever label you want to put on it, but the fact remains most of the Internet (see the Google data) is getting along quite happy without it. They don't need it today, they may not need it for years to come, IPv6 just doesn't have a compelling enough reason for people to invest in switching to it. |
Beta Was this translation helpful? Give feedback.
-
|
It's nearly the weekend where I am, so I'm dropping out of this thread to go do something relaxing. I've been around tech for several decades, I've seen a lot of technologies pumped as the only sensible way forwards only for folk just to go "No thanks" (e.g. Napster, BitTorrent, Crypto-Currencies, NFTs). Hopefully you've taken on board some of the points I've raised as to why there isn't a compelling reason for GH to implement IPv6. If you haven't then that's your choice, and I'll respect that, but personally I don't see IPv6 adoption happening any time soon for GH, and, honestly, I don't think most people will notice. |
Beta Was this translation helpful? Give feedback.
-
|
There are literally entire countries (none of which you are apparently aware of) who had to go native ipv6 due to ipv4 address exhaustion. So consider the equal-rights perspective. Non-"Western first-worlders" deserve equal access. Also, I'd love to have IPv6 everywhere since it would potentially make my intranet accessible from anywhere without needing to use tunnelling. (assuming proper security is set up, of course) But hey, it's an economic incentive to do better than Github. Open source copycats already provide most of the functionality. Hetzner and other hosts, as many have already stated, charges more for IPv4 so there is an economic incentive as well. That's actually how I originally discovered this was still an issue... Github is the Windows of the repo world. This is like Windows refusing to support USB-C, has no plans or ETA to support USB-C and just expects everyone to use alternatives... |
Beta Was this translation helpful? Give feedback.
-
|
RFC8200 Obsoletes RFC2460 which defined IPv6 as next generation. There is more and more v6 only services. If you can't reach them then that is on you and your ISP. IPv4 is obsolete in the same way as http is, everything should be https and IPv6, because that is current standards. |
Beta Was this translation helpful? Give feedback.
-
|
@alsutton you are talking stuff that you are not fully informmed. IPv4 IS legacy Internet Protocol ans that is not a tag some here want to put, but is what Internet Architecture Board states. Saying that doesn't mena IPv4 should be turned off immedially but efforts and resources should be put into make stuff availble in IPv6 and that a product that still has IPv4 only has a problem that must be fixed. |
Beta Was this translation helpful? Give feedback.
-
|
I can't believe that Github doesn't work with ipv6 in 2024. |
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
Out of this, multiple AS have only IPv6 because LANIC don't have anymore IPv4! Then nobody can access to github |
Beta Was this translation helpful? Give feedback.
-
|
The view is:Some people cannot get v4 anymore - that alone should be reason enough to move to at the very least dual stack…One could say: Actively refusing IPv6 is racist - but we don’t want to open this pandora box do we? ;)Am 28.08.2024 um 18:43 schrieb Al Sutton ***@***.***>:
To me it's sad to see folk limit the scope of their supporting evidence to data which backs their argument, and resort to attacking people, rather than coming up with globally relevant data to back their view.
To me it feels like this thread has become an IPv6 supporter echo chamber rather than somewhere that diverse viewpoints can be raised and objectively evaluated, hence why I test the waters by replying now and again, and then drop out when folk start using derogatory terms at people.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Please so not even try to imply that the inability to access a site which has always been IPv4 only is, in any way, like a disgusting attitude some folk have to their fellow human beings. You can buy access from IPv6 to IPv4 services via proxies, stopping racism is something that involves so much more than just money. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, absolutely normal to think people should pay additional to be able to use services like Github, owned by the leading tech company which proudly introduced IPv6 with Windows XP. And yes, if you believe people affected by the problem (mostly from not so rich countries) should pay extra money, then it's YOUR disgusting attitude towards your fellow human beings. Everything is well, you don't need to pay extra..... |
Beta Was this translation helpful? Give feedback.
-
|
and comments like that are why I leave the discussion rather than continue to debate the issue. Farewell for now. |
Beta Was this translation helpful? Give feedback.
-
It's like: |
Beta Was this translation helpful? Give feedback.
-
|
There are people and companies that are not doing their homework, they are still living in the Stone Age and are not evolving and are becoming complacent. Unfortunately, they promote the Internet's delay.
|
Beta Was this translation helpful? Give feedback.
-
|
Response #2 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
github moment |
Beta Was this translation helpful? Give feedback.
-
|
#Ipv6. We need IPV6 on github. Where is IPV6? Name: github.com |
Beta Was this translation helpful? Give feedback.
-
|
GitHub is still in the previous century .. just ran into this. |
Beta Was this translation helpful? Give feedback.
-
|
Oen problem is the people in general complain but don't have the guts to move their work out of Github. While many may still consider IPv6 important and this delay from Github unacceptable, at the end they just want to get their work done and don't want to have the work to move things elsewhere. |
Beta Was this translation helpful? Give feedback.
-
|
My work, as in, my private repos, is already moved off of Github and onto a private Gitlab instance. Lack of IPv6 wasn't the main reason (main reason was that I didn't want to pay for CI minutes), but it was one reason. My public work that I want others to see is still on my public Github. But neither of these really is the issue. The issue is that everyone else has all their code on Github, so if your code has dependencies to 10 other Github repos that need to be pulled to deploy your code, good luck moving that to Gitlab to be able to pull from an IPv6-only machine ... |
Beta Was this translation helpful? Give feedback.
-
|
Well, as mentioned you have to have guts to stick to things that you believe, otherwise it is just a discourse. If you believe in something and that is the right thing to do you find a way regardless how much effort that is. At the end example is important. |
Beta Was this translation helpful? Give feedback.
-
|
Just wanting to bring this to your attention @github, as there is a need for it. An update regarding your plans on this would be appreciated. |
Beta Was this translation helpful? Give feedback.
-
|
You perhaps didn't realize this, but the "@" + "github" string above spams all of us GitHub users, not the owners / admins of GitHub, as I suspect you intended... I know I didn't know that, until just now... |
Beta Was this translation helpful? Give feedback.
and others
-
Hi, I'm surprised I didn't find an existing discussion with this topic. Some services like github-releases.githubusercontent.com or user pages do support IPv6, however the webpage (github.com) itself, including cloning of git repositories, does not work.
Is there a public roadmap on enabling IPv6 for GitHubs very core business, distributing Git repositories? If I'm wrong and there is already IPv6 support, please guide me.
The same issues exists for api.github.com and thereby making CLIs unusable on IPv6 only connections.
Beta Was this translation helpful? Give feedback.
All reactions