NewsLab
Aug 28 15:48 UTC

GitHub Publishes IPv6 Addresses for Git SSH remotes (api.github.com)

54 points|by tonymet||16 comments|Read full story on api.github.com

Comments (16)

16 shown
  1. 1. tonymet||context
    see the "git" block for remote IPv6 ranges. This indicates they may be moving forward on ipv6 .

    "2a0a:a440::/29", "2606:50c0::/32",

  2. 2. rishabhyadav_||context
    Long overdue transition. Native IPv6 support for Git SSH remotes solves significant NAT bottleneck issues for automated CI/CD pipelines at scale.
  3. 3. avhception||context
    Well FINALLY!
  4. 4. aboardRat4||context
    What does this mean?
  5. 5. hadlock||context
    It means if your network is IPv6 native, you don't have to waste a very expensive IPv4 IP address, or proxy through one, to connect to it
  6. 6. aboardRat4||context
    Connect to what?

    dig AAAA guthub.com is still empty.

  7. 7. aaptel||context
    I know it's a typo but guthub is a hilarious name.
  8. 8. tonymet||context
    Maybe it’s German?
  9. 9. bzmrgonz||context
    I guess this helps the nomad crowd more than us cubicle jockeys right? Also iot? You guys can build ci/CD straight to iot edges.
  10. 10. KyleSanderson||context
    Bit of both, if you're building from a service provider you now don't need v4 to push (OVH, Hetzner, etc.)

    Less so than road warriors, who are typically CGNAT'd anyway.

  11. 11. crest||context
    It must be a snow day in hell.
  12. 12. 3r7j6qzi9jvnve||context
    There are ranges in the "git" block, but it doesn't mean they're doing anything with it (until it's in the DNS or they publish specific IPs are safe to connect to it doesn't mean anything)

    This page is actually in the wayback machine (thank you!!!) and the same ranges were already listed in 2022 (not in 2021, didn't look for exact first occurence)

    http://web.archive.org/web/20220710073458/https://api.github...

  13. 13. tonymet||context
    Good find , and also disappointing .
  14. 14. platesmead||context
    Great. I have a few IPv6-only hosts, and having to workaround GitHub being ipv4-only was a pain, especially during turnup, since my host config is stored on GitHub.
  15. 15. Macha||context
    And gone again (only IPv6 addresses there now are in the pages block). A short lived test? Or a bug/misconfiguration? GitHub has had no shortage of the latter unfortunately.
  16. 16. w3ll_w3ll_w3ll||context
    I can still se the IPv6 addresses in the git block