https://github.com/orgs/community/discussions/10539 Skip to content community Sign up * Product + Features + Mobile + Actions + Codespaces + Copilot + Packages + Security + Code review + Issues + Discussions + Integrations + GitHub Sponsors + Customer stories * Team * Enterprise * Explore + Explore GitHub + Learn and contribute + Topics + Collections + Trending + Skills + GitHub Sponsors + Open source guides + Connect with others + The ReadME Project + Events + Community forum + GitHub Education + GitHub Stars program * Marketplace * Pricing + Plans + Compare plans + Contact Sales + Education [ ] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this organization All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up {{ message }} @community GitHub Community * Overview * Repositories * Discussions * Packages * People More * Overview * Repositories * Discussions * Packages * People IPv6 support for cloning Git repositories #10539 Unanswered aparcar asked this question in General IPv6 support for cloning Git repositories #10539 @aparcar aparcar Jan 25, 2022 * 21 answers * 18 replies Return to top [160] aparcar Jan 25, 2022 - 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. 161 You must be logged in to vote 63 5 6 [?] 11 5 8 Replies 21 suggested answers * 18 replies Oldest Newest Top edited [750] ffrediani Jan 25, 2022 - I am unable to understand what in 2022 still holds full IPv6 support for a platform like GitHub. Even if there is already a work in progress for this it is more useful to disclose a proper ETA rather than a "we are working on it" with no ETA. Thanks Beta Was this translation helpful? Give feedback. 36 You must be logged in to vote 0 replies [807] ayubio Jan 25, 2022 - 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. 48 You must be logged in to vote 0 replies [547] DanielDamito Jan 25, 2022 - I really tried to use github in a IPv6 Only Network and I was not successful. We are not talking about a new feature request or a little detail, we are talking about the current standard protocol of the Internet defined by IANA. Is there any plan on the github's roadmap to fully adopt IPv6? Beta Was this translation helpful? Give feedback. 19 You must be logged in to vote 0 replies [124] NiKiZe Jan 26, 2022 - 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. 13 You must be logged in to vote 0 replies [353] andrediashexa Jan 28, 2022 - IPv6 is the actual internet protocol, while IPv4 is a legacy protocol. Please, priorize this request. Beta Was this translation helpful? Give feedback. 26 You must be logged in to vote 9 0 replies [171] maxadamo Feb 10, 2022 - Beta Was this translation helpful? Give feedback. 1 You must be logged in to vote 6 replies @aparcar aparcar Feb 10, 2022 Author - I don't understand what you're trying to say. Beta Was this translation helpful? Give feedback. @aparcar aparcar Feb 10, 2022 Author - I'm sure they're doing some smart load balancing which could make it harder to migrate, surely there is more involved than a single IPv6 checkbox. Beta Was this translation helpful? Give feedback. @ffrediani ffrediani Feb 10, 2022 - Easy or complex there are not much explanations of why in already 2022 there is no IPv6 implemented yet. Whatever needs to be done is business as usual and should have been already planned and implemented in the recent years, therefore it is late already. I believe it can be easily said company infrastructures like Google, Facebook or Netflix are fairly complex and they all have 100% support in the frontend for a while. Beta Was this translation helpful? Give feedback. View more [404] angerman Mar 15, 2022 - 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. 10 You must be logged in to vote 0 replies [350] BroOtti May 18, 2022 - 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. 13 You must be logged in to vote 1 reply @MrLawrence MrLawrence Jul 19, 2022 - No, no. It's apparently just more important to rename the "master" branch to "main". Beta Was this translation helpful? Give feedback. 8 6 [750] ffrediani May 18, 2022 - Probably because people that manage the technical team still didn't realize what this mean and didn't prioritize it enough. Every time I get as an answer that something like "there are many complex things that must be taken into account and it is not easy to adust everything to make it happen. It is in the roadmap" 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 ? The lack of these answers makes it look like that is being treated as something minor or less important. 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. 10 You must be logged in to vote 2 3 replies @dwmw2 dwmw2 May 18, 2022 - 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. 1 @NiKiZe NiKiZe May 18, 2022 - Totally agree! Defined as current in RFC8200 Beta Was this translation helpful? Give feedback. @BroOtti BroOtti May 18, 2022 - 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. 2 edited [241] xtaran Jun 9, 2022 - 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 ipv6.github.com -- which exists, but is just a (probably wildcard-) dummy page which just points to https://ipv6.github.io/ (likely also a DNS wildcard) which then just states that there is no content yet. Probably because it (nowadays?) belongs to the Github user @IPv6. And the Wayback Machine only has a record from 2022 of that site. Maybe someone else remembers where that talk or blog posting was published. 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 github-ipv6.com which worked as a reverse proxy according to this Reddit comment, but since it no more exists, I guess they got a DCMA takedown or cease-and-desist noticed for using the Github trademark. 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: - host -t AAAA gitlab.com gitlab.com has IPv6 address 2606:4700:90:0:f22e:fbec:5bed:a9b9 Beta Was this translation helpful? Give feedback. 11 You must be logged in to vote 4 0 replies [777] MeesJ Jul 7, 2022 - 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. 12 You must be logged in to vote 2 1 reply @danielehrhardt danielehrhardt Jul 22, 2022 - Biggest fail i ever saw. Beta Was this translation helpful? Give feedback. 1 edited [649] TheBlueMatt Jul 23, 2022 - 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. 13 You must be logged in to vote 1 0 replies [478] lalelunet Jul 30, 2022 - 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. 4 You must be logged in to vote 0 replies [127] sushlala Jul 31, 2022 - How can you not have ipv6? Some cloud providers charge extra for ipv4! Beta Was this translation helpful? Give feedback. 8 You must be logged in to vote 0 replies [619] madalinignisca Aug 10, 2022 - 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. 8 You must be logged in to vote 0 replies [723] Manouchehri Aug 17, 2022 - Could we possibly just have a proxy service for Git over HTTPS cloning? Even read-only cloning of public repos would be quite helpful for building on IPv6-only servers. Beta Was this translation helpful? Give feedback. 5 You must be logged in to vote 1 reply @NiKiZe NiKiZe Aug 17, 2022 - Have requested this as well. But nope, no communication at all... Looking at alternatives. Beta Was this translation helpful? Give feedback. [332] DanWin Aug 20, 2022 - Since there is still no official response, I've decided to provide a proxy myself. Feel free to clone via my proxy. More details here: https://danwin1210.de/github-ipv6-proxy.php Beta Was this translation helpful? Give feedback. 7 You must be logged in to vote 3 [?] 4 2 replies @steffann steffann Aug 24, 2022 - I personally don't like it when a party in the middle can decrypt the TLS session. I would prefer if the connections were just TCP proxied on the standard ports so that it would be possible to just add GitHub.com to /etc/hosts with an IPv6 address. I did something similar in the past, but got a cease-and-desist :) To be fair, that was more about me registering github-ipv6.com than anything else :D Maybe we can set up a bunch of TCP-proxies and provide a global service! As long as we don't call it GitHub-something.com ;) Beta Was this translation helpful? Give feedback. @steffann steffann Aug 24, 2022 - Thinking about that, my friend Jan Zorz has a public NAT64 gateway that works perfectly for this. Just plain IPv6 to IPv4 translation, without even looking at the TCP payload! Add this to your /etc/hosts and you're done! 2001:67c:27e4:1064::140.82.121.3 github.com www.github.com Beta Was this translation helpful? Give feedback. 1 [135] Kleissner Aug 24, 2022 - It is absolutely time for IPv6 support. According to Google https:// www.google.com/intl/en/ipv6/statistics.html we are at 40% worldwide deployment right now. Many here asked why. My personal guess would be they run legacy hardware and software stack, that don't natively support IPv6, and at GitHub internally it may not simply be "turn on the IPv6 switch", but rather replace these 200 routers and perhaps re-develop some pieces of internal software. We are all developers here, so no need to explain the obvious, that re legacy applications from the 00s built only for IPv4 it may be better to just redevelop the whole thing with a modern software stack. Who knows what skeletons they have in their closet, but chances are if it was just flipping a switch, they would have done so already. Probably it is as much an organizational and prioritization problem, as it is a tech one. Beta Was this translation helpful? Give feedback. 7 You must be logged in to vote 2 replies @illiliti illiliti Aug 24, 2022 - My personal guess would be they run legacy hardware and software stack It's highly likely that your guess is right. And that's concerning because legacy is insecure and poorly maintained cruft. I wouldn't trust github your personal data... Beta Was this translation helpful? Give feedback. [?] 2 @NiKiZe NiKiZe Aug 24, 2022 - My bet is on logging and abuse prevention. Lack of IPv6 could be ok, but lack of communication about IPv6 is not ok. Beta Was this translation helpful? Give feedback. 1 [750] ffrediani Aug 24, 2022 - Whatever skeletons they may still have there are not excuses of complexity or whatever to be so late at this stage. Several even more complex scenarios to mention as Google, Facebook, Netflix, Akamai, etc all have full IPv6 support on their services. Beta Was this translation helpful? Give feedback. 6 You must be logged in to vote 0 replies edited [300] cooperlees Aug 24, 2022 - Via being a paying personal customer and my company also being a paying customer, I've logged this request via our support multiple times. I've even asked at GitHub events. Each time getting very little reason as to why we can't have Git operations (that are mainly SSH and HTTPS) over IPv6. There was responses it was in the works, and even a brief discussion about my company helping to test it. That just all fell away and I was never given an estimated time for this to happen. Please GitHub lets get a plan of action underway for this. It's bit me time and time again. I'm sick of running dual stacked proxies to just access very few things, GitHub being one. Beta Was this translation helpful? Give feedback. 6 You must be logged in to vote 1 0 replies [503] kkimdev Aug 24, 2022 - Any security risk with a third party proxy? Beta Was this translation helpful? Give feedback. 2 You must be logged in to vote 2 replies @danopia edited danopia Aug 24, 2022 - Speaking to HTTPS: ([DEL:similar might apply for SSH:DEL]) * If a proxy has its own TLS certificate, I'd suggest against sending authenticated requests thru it. Anonymously cloning a public repo sounds fine to me, but I suppose it's technically possible for clone tampering to happen, so maybe check the githash. * If a proxy just passes through Github's TLS - if you set it up by editing /etc/hosts - then there should be end-to-end encryption between you and Github and therefore minimal security risk. + For example TransIP operates a private Github IPv6 proxy for their customers which is transparent and does not pose a security risk. TransIP also mentions that third party proxies might have their own issues: We have no control on whether or not Github will for example rate limit our proxy. As such, we offer no warrantees on its continued functionality and instead implore Github to support IPv6. Personally, I pay my VPS provider for an hour of IPv4 every time I need to run git push :) Beta Was this translation helpful? Give feedback. @steffann steffann Aug 24, 2022 - Depends on the layer that the proxy works: * A layer-7 HTTPS proxy terminates the encryption, decrypts it and re-encrypts it. It can therefore see everything that happens on the connection, and even modify the data on the fly. * A layer-4 TCP proxy will not be able to do this. It established a new TCP session, but its contents are forwarded as-is, encrypted by GitHub and only decryptable by the client, and not by the proxy in between. * A layer-3 NAT64 gateway will not even terminate the TCP connection but forward every packet between GitHub and the client as-is, and therefore is the least invasive. The HTTP proxy as shown by @DanWin can see your traffic to/from GitHub and therefore could do nasty things. I doubt that @DanWin does this, but if you're talking about risk then yes, there is a risk. The SSH proxy @DanWin shows is NOT a risk, as the encryption is done by GitHub and not modified by the proxy. You can check the SSH fingerprints and verify that you are talking to the authentic GitHub servers. Beta Was this translation helpful? Give feedback. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Category :octocat: General Labels General 26 participants @aparcar @angerman @danopia @xtaran @kkimdev @steffann @madalinignisca @MrLawrence @TheBlueMatt @dwmw2 @NiKiZe @maxadamo @cooperlees @DanWin @lalelunet @Manouchehri @ffrediani @sushlala @Kleissner @danielehrhardt @BroOtti and others Add heading text Add bold text, Add italic text, Add a quote, Add code, Insert Link Link Text [ ] URL [ ] Add Add a link, Add a bulleted list, Add a numbered list, Add a task list, Directly mention a user or team Reference an issue or pull request Add heading text Add bold text, Add italic text, Add a bulleted list, Add a numbered list, Add a task list, 1 reacted with thumbs up emoji 1 reacted with thumbs down emoji 1 reacted with laugh emoji 1 reacted with hooray emoji 1 reacted with confused emoji [?] 1 reacted with heart emoji 1 reacted with rocket emoji 1 reacted with eyes emoji Footer (c) 2022 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.