817
submitted 1 year ago* (last edited 1 year ago) by carrylex@lemmy.world to c/programmer_humor@programming.dev

Context:

People have been asking for IPv6 Support on GitHub since years (probably a decade by now)

... and someone even got so annoyed that they decided to setup a dedicated website for checking this: https://isgithubipv6.live/

top 50 comments
sorted by: hot top controversial new old
[-] chris@l.roofo.cc 90 points 1 year ago

The perpetual chicken egg problem of IPv6: many users don't have IPv6 because it's not worth it because everything is reachable via IPv4 anyways because IPv6 only service don't make sense because they will only reach a subset of users because many users don't have IPv6.....

[-] Album@lemmy.ca 20 points 1 year ago* (last edited 1 year ago)

Honestly this isn't even true anymore. Most major ISPs have implemented dual stack now. The customer doesn't know or care because it's done at the CPE for them.

I use a browser extension which tells me if the site I'm at is 6 or 4 or mixed. In 2024 most major sites support V6. A lot of this is due to CDN supporting it natively.

The fact that GitHub doesn't is quickly becoming the exception.

[-] serpineslair@lemmy.world 11 points 1 year ago

May I ask which extension you are using?

load more comments (2 replies)
load more comments (2 replies)
[-] takeda@lemmy.world 13 points 1 year ago

If IPv6 is done right you don't even know you have it. If you use a cell phone or a home Internet, there is a high chance you are already using IPv6.

load more comments (2 replies)
load more comments (2 replies)
[-] henfredemars@infosec.pub 55 points 1 year ago* (last edited 1 year ago)

I’m not using it because by and large it’s not implemented properly on consumer hardware, and my ISP doesn’t care if their IPv6 network is broken.

[-] MagicShel@programming.dev 38 points 1 year ago

I've tried multiple times to go IP6 only. I mostly thought, despite my reasonable understanding of IP4, that I was the problem in trying to set it up. I found my dns host was being forgotten multiple times a day, set to something invalid, then it would time out and revert back to the working one. I couldn't figure out how to connect two computers together for Minecraft.

Now I hear it was just garbage consumer hardware and software? Fuck me. So much wasted time and effort to say nothing of believing I had turned into a tech idiot.

[-] henfredemars@infosec.pub 28 points 1 year ago* (last edited 1 year ago)

You’re not an idiot. You’re using tools that don’t really do what they claim because it wasn’t considered an important use case.

IPv6 is great, but we haven’t seen enough pain yet to really drive adoption on the home LAN.

My solution uses the ISP box to deliver stateless auto conf, and bridging a consumer router. I can’t open ports but at least I get an IP.

load more comments (5 replies)
[-] skilltheamps@feddit.de 10 points 1 year ago

That is not the case for every country though. In France and Germany for example almost 3/4 of google requests are via IPv6.

load more comments (7 replies)
[-] GTG3000@programming.dev 53 points 1 year ago

"Everyone is using IPv6"

It's barely supported. Most providers here "offer IPv6", but each has a different gotcha to actually using it, if it works at all and they didn't just route you through hardware that doesn't know what it is.

[-] flying_sheep@lemmy.ml 21 points 1 year ago* (last edited 1 year ago)

What's “here”? Here in Germany, mine has it for maybe 10 years or so. Basically since launch day.

And new ISPs only have v6 since all legacy (v4) blocks have been sold years ago.

[-] person420@lemmynsfw.com 11 points 1 year ago

Just because you have a IPv6 address doesn't mean you're actually using it. At best you're tunnelling IPv4 traffic through your carrier's IPv6 network. Current estimates (from Cloudflare) show only about 34% of the global internet uses IPv6.

If you only used IPv6, you wouldn't be able to access nearly 66% of the internet.

load more comments (10 replies)
[-] RecluseRamble@lemmy.dbzer0.com 44 points 1 year ago* (last edited 1 year ago)

Why should we care? So address space may run out eventually - that's our ISPs' problem.

Other than that I actually don't like every device to have a globally unique address - makes tracking even easier than fingerprinting.

That's also why my VPN provider recommends to disable IPv6 since they don't support it.

[-] MrRazamataz@lemmy.razbot.xyz 30 points 1 year ago

Because people in countries with ISPs that are unable to provide IPv4 (e.g. too expensive) can't access GitHub easily.

[-] laughterlaughter@lemmy.world 11 points 1 year ago

even easier then fingerprinting.

than*

load more comments (1 replies)
load more comments (22 replies)
[-] VitabytesDev@feddit.nl 40 points 1 year ago

My ISP doesn't provide an IPv6 connection.

[-] ytg@sopuli.xyz 24 points 1 year ago

Mine provides a connection, but doesn’t expose ports on v6. So I can access v6 services but can’t self-host any.

load more comments (3 replies)
load more comments (13 replies)

rose are red, violets are blue, money is the reason we can't have nice things.

[-] UntitledQuitting@reddthat.com 10 points 1 year ago

Roses in summer, violets in spring, it’s trivially easy this rhyming thing

load more comments (3 replies)
[-] bigredcar@lemmy.world 21 points 1 year ago

Just remember we got rid of TLS 1.0 the same thing can be done with IPv4. It's time for browser makers to put "deprecated technology" warnings on ipv4 sites.

[-] NocturnalEngineer@lemmy.world 68 points 1 year ago

IPv4 isn't depreciated, it's exhausted. It's still a key cornerstone of our current internet today.

We still have "modern" hardware being deployed with piss-poor IPv6 support (if any at all). Until that gets fixed, adoption rates will continue to be low. Adding warnings will only result in annoying people, not driving for improvement.

load more comments (4 replies)
[-] AeonFelis@lemmy.world 16 points 1 year ago

I'll start using it after I migrate to Wayland.

[-] starman@programming.dev 15 points 1 year ago

How do you guys remember IPv6 addresses?

[-] bfg9k@lemmy.world 31 points 1 year ago

You shouldn't need to remember IP addresses, they invented DNS to solve that problem lol

Even so, the addresses can be even easier to remember because we get a-f as well as digits, my unique local subnet is fd13:dead:beef:1::/60 cause I like burgers haha

[-] SpaceCadet@feddit.nl 21 points 1 year ago* (last edited 1 year ago)

You do need to know it when you're working with subnets and routing tables.

Unless you have anything but a flat network structure with everything in one subnet, working with IPV6 is a giant PITA.

load more comments (5 replies)
load more comments (4 replies)
[-] mindlight@lemmynsfw.com 11 points 1 year ago

2 months ago I thought I'd start learning IPv6 and started watch some intro videos on YouTube.

Holy crap... It's a beast and it just felt like if you don't know what you're doing you might lose all control over your network. Ok. So a device didn't get a dhcp address? No problem... It creates it's open IP address and starts talking and try to get out on internet on its own....

Normally that's not a problem since your normal home router wouldn't route 169.254.x.x.... But it just seems like there's A LOT to think about before activating IPv6 at home. I've got a Creality K1 Max... Fun thing: factory reset also creates a new MAC Address... So there's no way in hell thay I just let her lose by activating IPv6.

Ps. Yes, I most likely panic because I haven't figured out IPv6... But until I understand IPv6 there's just going to be IPv4.

[-] sloppy_diffuser@sh.itjust.works 10 points 1 year ago

Ok. So a device didn't get a dhcp address? No problem... It creates it's open IP address and starts talking and try to get out on internet on its own....

Its not that different from a conceptual point of view. Your router is still the gate keeper.

Home router to ISP will usually use DHCPv6 to get a prefix. Sizes vary by ISP but its usually like a /64. This is done with Prefix Delegation.

Client to Home Router will use either SLACC, DHCPv6, or both.

SLACC uses ICMPv6 where the client asks for the prefix (Router Solicitation) and the router advertises the prefix (Router Advertisement) and the client picks an address in it. There is some duplication protection for clients picking the same IP, but its nothing you have to configure. Conceptually its not that different from DHCP Request/Offer. The clients cannot just get to the internet on their own.

SLACC doesn't support sending stuff like DNS servers. So DHCPv6 may still be used to get that information, but not an assigned IP.

Just DHCPv6 can also be used, but SLACC has the feature of being stateless. No leases or anything.

The only other nuance worth calling out is interfaces will pick a link local address so it can talk to the devices its directly connected to over layer 3 instead of just layer 2. This is no different than configuring 169.254.1.10/31 on one side and 169.254.1.11/31 on the other. These are not routed, its just for two connected devices to send packets to each other. This with Neighbor Discovery fills the role of ARP.

There is a whole bunch more to IPv6, but for a typical home network these analogies pretty much cover what you'd use.

load more comments (2 replies)
load more comments (3 replies)
[-] JATtho@lemmy.world 10 points 1 year ago

I'm actually bit sad that I had to move onto a ISP which has zero IPv6 support, as I previously did have IPv6. The last thing I did on that connection was to debug the hell out of my IPv6 code I had developed.

load more comments (2 replies)
load more comments
view more: next ›
this post was submitted on 09 Jun 2024
817 points (98.1% liked)

Programmer Humor

26772 readers
1405 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS