GitHub Community
Replies: 126 comments 294 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.
-
|
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.
-
|
Github had better not implement IPv6 or it will break my workflow: in my scripts I always use github.com AAAA to probe if DNS64 is working. P.S. Yeah, I know about ipv4only.arpa, but github.com is more reliable. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
They are already further ahead, but apparently, gitlab also has problems with IPv6. No CI/CD in v6 if you use their runners (we ran into the problem a few days ago) https://gitlab.com/gitlab-org/gitlab-runner/-/issues/37419 To follow to |
Beta Was this translation helpful? Give feedback.
-
|
I cannot confirm this. We‘ve been using IPv6 in GitLab CI with the Docker executer for a while now without any issues. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also surprised about this. Maybe it broke recently? As you can see in the output of the ticket, it seems like IPv6 was implemented. But the route is unreachable. (maybe you can comment on the ticket ;-) ) |
Beta Was this translation helpful? Give feedback.
-
|
It definitely still works. I also don‘t think this is something GitLab can break as all network related stuff is part of either Docker or the Kernel, not GitLab. I’ve added a comment with further info to your GitLab issue. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Any updates? |
Beta Was this translation helpful? Give feedback.
-
|
Nope. Github still broken. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hah, now the caused me to laugh .. nice! 😄 |
Beta Was this translation helpful? Give feedback.
-
|
We (a small LIR/ISP in USA) just opened a support ticket, our new networks are IPv6 only. Have to say, this was unexpected. |
Beta Was this translation helpful? Give feedback.
-
|
Github support replied that they do not have plans for adding IPv6 right now 🤷♂️. |
Beta Was this translation helpful? Give feedback.
-
|
They did a try not too long ago to activate it though.... |
Beta Was this translation helpful? Give feedback.
-
|
give microsoft some time, they still have to hunt some russian hackers, giving them even more IPs to hack sounds like a nightmare I can not support. On the other hand, McGiver probably would've setup a janky ipv6_2_ipv4 proxy infront of everything wanting to git clone and deal with the real integration during a commercial break. Also +1 for this entire discussion to be archived #archiveprogram section hall of wonders |
Beta Was this translation helpful? Give feedback.
-
|
Russian hackers are valid target for CIA and FBI, depending where they are, so no excuse for lame irony |
Beta Was this translation helpful? Give feedback.
-
|
Dude, I switched my EC2 from IPv4 to 6 because they started charging. Now I can't pull changes from github repos because github won't support it. |
Beta Was this translation helpful? Give feedback.
-
|
What about switching to AWS CodeCommit and then using a sync operation from GitHub to CodeCommit. https://github.com/marketplace/actions/github-to-aws-codecommit-sync |
Beta Was this translation helpful? Give feedback.
-
|
None of the 3 options, they are terrible. I strongly recommend giving up on github and finding another tool while someone sensible, up-to-date, convinces GitHub of the urgent need to enable IPv6 in your services. |
Beta Was this translation helpful? Give feedback.
-
|
it's not an option for those who collaborate |
Beta Was this translation helpful? Give feedback.
-
|
@santosh This change was the best option you made, be sure of that. Any investment today in IPv4 is doomed to failure. |
Beta Was this translation helpful? Give feedback.
-
|
Use one of the NAT64 gateways, just add a row in your HOSTS file, or use their DNS64. |
Beta Was this translation helpful? Give feedback.
-
|
Those who really collaborate, ditch a greedy and ignorant corporate service in favor of one, that truly collaborates by using up-to-date protocols and no legacy-protocols…Am 26.04.2024 um 21:11 schrieb Tony Metzidis ***@***.***>:
it's not an option for those who collaborate
—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.
-
|
The fact that one of the important pieces of developer infrastructure is not ready for IPV6, which is now 29 years old, is plainly unacceptable! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Now, they have added http3. Still no IPv6 |
Beta Was this translation helpful? Give feedback.
-
|
AWS Lightsail ipv6only not able to |
Beta Was this translation helpful? Give feedback.
-
|
welcome to our support group. |
Beta Was this translation helpful? Give feedback.
-
|
Since AWS started charging for public IPv4 addresses, I was confidently switching my entire infra to IPv6 only. |
Beta Was this translation helpful? Give feedback.
-
|
It's mind-blowing that is this over a year old, and not a single word of communication from GH. |
Beta Was this translation helpful? Give feedback.
-
|
Well, they tried enabling it not that long ago. But this is clearly not given the attention needed. At the same time, what can they do? Say they tried and failed? |
Beta Was this translation helpful? Give feedback.
-
They did preparations for enabling which caused some issues for some customers, they are probably far from ready (hope I'm wrong) But yes, they are not putting the resources that they should on this. |
Beta Was this translation helpful? Give feedback.
-
|
They probably should hire someone from the GitLab infra team. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Using Hetzner cloud here and I can't even just migrate to another git host because I rely on external repos from github :( |
Beta Was this translation helpful? Give feedback.
-
|
are you locked to Github just because Hetzner pushes it upon you? |
Beta Was this translation helpful? Give feedback.
-
|
No, many programming languages and repos rely on packages/repos that are hosted on Github. Hetzner simply follows supply and demand: ipv4 adresses are getting rarer and rarer and thus they ask a price for it. |
Beta Was this translation helpful? Give feedback.
-
I’m locked to GitHub because of nixpkgs and Hetzner, like others charges extra for IPv4 addresses. |
Beta Was this translation helpful? Give feedback.
-
|
I wonder if there's conflict of interests here. We all rely on Github public repos. Llama3 70B: Azure and co earn a few $ per month per IPv4. |
Beta Was this translation helpful? Give feedback.
-
|
Well, yes. But that would be stupid. Because they would also make a favor to the competitors that also have v4 (AWS has a few). +, as this becomes more widely known, more and more people are going to consider that when starting new projects/company's from scratch and they will eventually end up losing market share as the price of v4 rises. If they had a killer feature that the others don't have, I don't say. But they don't. Even dependabot can run off github these-days |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that's the case. Our company and many other companies have now switched to gitlab.com because of this problem. Most of it has been adapted for IPv6. The “Container Registry” is still working on an IPv6 conversion, but the process is completely open, at least in contrast to the process at GitHub, and everyone can read the current status / the developer attached to the ticket and also the comments of the developers themselves. So if you have the opportunity, I would recommend gitlab because GitHub has not yet commented on the topic and it may take years until it is implemented. |
Beta Was this translation helpful? Give feedback.
-
|
@Darragh-McCarthy although that may be true I don't think that is the case of a conflict of interest. I bet that it is just bad technical management from Github whose individuals there are unable to understand the bare minimum they need in order to put this as a higher priority and make it happen once of all. The season for "the environment is complex and it needs to be done with care" has passed a long time ago. |
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