GitHub Community
Replies: 174 comments 424 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.
-
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.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
No. Nobody needs assistance in understanding how IPv6 works. Please stop this spam, as I already said in my comment two weeks ago: https://github.com/orgs/community/discussions/10539#discussioncomment-11684249 |
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.
-
|
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.
-
|
Can we please stop with these "what specific issue do you have due to lack of IPv6". There's no "help" that people operating IPv6-only servers need. The issue is you need to pay for IPv4 addresses for all your servers to reach Github. Tons of backend-only servers don't need IPv6 except for accessing Github. |
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.
-
|
Yes. Multiple people moved their projects to Gitlab because they want to access them from IPv6-only machines. |
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.
-
|
If you only want to download something from github one could use https://gh-v6.com/ as a workaround. |
Beta Was this translation helpful? Give feedback.
-
|
@mph4 The community understands ipv6 is a big project, and it seems there has been some active work on the upgrade about 6 months ago. What could we do to help improve the updates on this? Even a quarterly progress report would do a lot for this community. There are a number of charity projects providing ipv6 workarounds, like gh-v6 , https://danwin1210.de & isgithubipv6 . Lots of passionate customers & open source contributors are rooting for a solution! |
Beta Was this translation helpful? Give feedback.
-
|
And that is only the insecure GH proxy's (they might in theory log or manipulate data going thru them) but there is also several NAT64 solutions posted above that can be used with GH certificates and fingerprints in place, almost eleminating the mitm vector. Please GH, make sure that your users and customers do not get into security issues when using third party solutions. Instead ensure that you yourselves provide a solution, even if it at this time don't have to be to enable IPv6 top-level. |
Beta Was this translation helpful? Give feedback.
-
|
"The community understands ipv6 is a big project" |
Beta Was this translation helpful? Give feedback.
-
|
GitHub unsupported. GitHub is not secure as the only method to access it is to use insecure 3rd party proxies. Or 3rd parties tunnels over modifying /etc/hosts. What is the conspiracy? Reptiloids? |
Beta Was this translation helpful? Give feedback.
-
|
...@andres-moya, what? |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
@JorenVsyntra, don't spam peoples’ e-mail inboxes for that. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
It gives a certificate for googlezip.net |
Beta Was this translation helpful? Give feedback.
-
Okay, sorry, then i remove it |
Beta Was this translation helpful? Give feedback.
-
|
wow ... almost 3 years later and still not f.....g IPv6 on github.com |
Beta Was this translation helpful? Give feedback.
-
|
Still no updates? No IPv6 available? It's almost 2025! Come on! This is unacceptable. This is legacy IP offending. |
Beta Was this translation helpful? Give feedback.
-
The techies surely do get it. But it seems like they do not have (enough) say. Being a techie myself, I surely do not want to support that, neither by using their stuff nor by promoting/fixing it. |
Beta Was this translation helpful? Give feedback.
-
|
@tonymet they are measuring it wrong. This normally happens when not the most qualified people are in charge. |
Beta Was this translation helpful? Give feedback.
-
You may be right, but changing their mind on that is even less likely than convincing them to adopt ipv6, so why bother? |
Beta Was this translation helpful? Give feedback.
-
how about the dependencies? |
Beta Was this translation helpful? Give feedback.
-
Exactly. We will have to resort to proxies (very use-case specific, typically) until enough people move off GH or GH decides to be a serious product/solution. Most unfortunate. |
Beta Was this translation helpful? Give feedback.
-
|
Microsoft's decision not to invest figuring out IPv6 on its infrastructure like other providers will no doubt cost them greatly. When the opportunity cost of holding their IPv4 allocation for GitHub internals is worse than just investing in IPv6 I'm sure we will see some progress on this, likely 5 or 10 years away however. |
Beta Was this translation helpful? Give feedback.
-
I don't know how the internals are designed but probably it's possible to run them indefinitely on IPv4 using only private networks (no public IPv4 addresses). This has no relevant opportunity cost. |
Beta Was this translation helpful? Give feedback.
-
|
What the heck is up with the recent comments here? I got emails from the last couple minutes for new comments from @Jahtribe3, @naimul1211, @aa131520, @kanahamppari, @lppppu, @Reunt who are all commenting on old comment chains, with text that A) sounds AI-generated, B) is useless, and C) all imply that the issue is on the user's side, not on Github. Please stop spamming this issue report with your bot-generated comments. I find it unlikely that five people with similarly-meaningless profiles and similarly meaningless empty template repos on their profiles all start commenting similarly-irrelevant comments here. This is just spamming people with useless notification mails. This issue is for the fact that Github still has no IPv6 support, ~15 years after they should have added it. It's not for bots to convince people to just downgrade to IPv4 or to sell services to migrate away from Github or whatever the purpose of your comments is. |
Beta Was this translation helpful? Give feedback.
-
Speaking from experience, this is actually EXACTLY how actual GitHub/Microsoft (sales) people react. |
Beta Was this translation helpful? Give feedback.
-
|
@rettichschnidi, these ones aren't real. I implore you view the |
Beta Was this translation helpful? Give feedback.
-
|
I'm not disputing that those are ("AI") bots. But what comes from MS, in my experience, sounds uncannily similar to what those (now deleted) messages contained. |
Beta Was this translation helpful? Give feedback.
-
|
Happy new year 2025 ! |
Beta Was this translation helpful? Give feedback.
-
|
That is true - if you write your software with that abstraction level, that can happen. You can write new software that might be resistant / automatically adopt to a future IPv8 or IPv10 release. But you can NOT do anything about the old software that people developed with only IPv4 in mind. There was nothing the designers of IPv6 could have done differently to make old software, which deliberately uses IPv4 APIs, support IPv6 without any changes to the software. |
Beta Was this translation helpful? Give feedback.
-
|
A windows application that uses the Win32 API to "give me a TCP connection to this host(name)" is compatible with IPv6, as long as it doesn't try to use ipaddresses anywhere. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah. As I said, that would be an example of an app that is resistant to protocol changes and will probably also adopt to an IPv8 in the far future. But the point is, old software usually isn't written that way. Sure, a simple client might work that way, but a ton of software has stuff like IP white- or blacklists or other stuff where that simple trick stops working and your app will have some kind of protocol-dependant functionality. |
Beta Was this translation helpful? Give feedback.
-
No competent software engineer has written such software in the 21st century. We've had getaddrinfo() and friends for about as long as we've had IPv6, since the final decade of the 1900s. |
Beta Was this translation helpful? Give feedback.
-
|
I agree. But as we can see with Steam and Discord, A) not every software is written by competent software engineers and B) we have tons of software that was written in the 20th century. Also, even with getaddrinfo, if your software loads whitelists / blacklists from a config file, chances are high that it has validity checks for the config file and checks if an IP is valid and doesn't just pipe it into a network API, so it would need changes for IPv6 compatibility. |
Beta Was this translation helpful? Give feedback.
-
|
Minimal added value???????You’re clearly delusional (or are under the influence of heavy drugs) if you don’t see the value at SO many levels…But hey - stick with v4 and get replaced by „a newer, more performant model“ granddad rather sooner than later… We almost hit the critical mass - after that the world will migrate so freakin fast that anyone not being able to go v6 only instantly is irrelevant and left behind.There’s a reason that the Dinosaurs went extinct and life found a better approach ;)Am 08.01.2025 um 21:10 schrieb Tony Metzidis ***@***.***>:
They decided to break backward compatibility knowing ahead of time it was a kernel and firmware upgrade so the migration would be more challenging. The designers could have supported ipv4 headers in ipv6 but instead chose the shaming approach despite minimal added value
—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.
-
|
GitHub is one of the main keys to unlock ipv6 in many corporations. And GitHub missing ipv6 is one of the main excuse for said corps. It is sad GitHub's future ended in the hands of sales people. Instead of showing Microsoft as our champion, it's worsening Microsoft image in the community. Customers are needing ipv6 in the most interesting markets for growth and more gouvernements are adding it as prerequisite to consider a provider. |
Beta Was this translation helpful? Give feedback.
-
Insulting an opponent is not the best way of discussion |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Nope. There is a fundamental difference, declared in the common rule of healthy discussions: focus on the problem, not the person. |
Beta Was this translation helpful? Give feedback.
-
|
A healthy discussion should be based on facts and not strange claims. |
Beta Was this translation helpful? Give feedback.
-
|
Common rule of discussion also states that nonsense shouldn’t be propagated into the wild - if the truth hurts your feelings that hard it maybe means that you already know you are wrong and are just searching for more nonsense arguments to strengthen an already broken opinion… With that being said I didn’t want to insult on a personal level - but calling IPv6 a „minimal added value“ is just delusional and will get you a professional pimp-slap in the face ;) And you know it!Am 09.01.2025 um 08:05 schrieb Mykola Dzham ***@***.***>:
However about statements like
Minimal added value
which has more distance to reality than Trump to dignity could be said the same.
Nope. There is a fundamental difference, declared in the common rule of healthy discussions: focus on the problem, not the person.
—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.
-
|
It pains me that I have just spun up an (increasingly common) IPv6-only VM instance, only to find I cannot curl a package I need from a GitHub repo. Please do better, GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
I'm really going crazy too, my ISP's IPv4 and IPv6 network speeds are not equal, IPv4 network speed is almost limited to the point that it can't be used, only IPv6 is normal. And ISP don't offer NAT64 and DNS64 for IPv6. But Github doesn't provide IPv6, so I only have a few hours a day to open Github normally, and most of the time the connection times out. I suggest that Github support IPv6 as soon as possible, otherwise IPv4 will affect the use too much! |
Beta Was this translation helpful? Give feedback.
-
|
For reference, which country and ISP is this? |
Beta Was this translation helpful? Give feedback.
-
|
I've opened a related feature request / discussion: |
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