this post was submitted on 09 Jun 2024
9 points (100.0% liked)

Programmer Humor

19315 readers
2 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 1 year ago
MODERATORS
 

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 28 comments
sorted by: hot top controversial new old
[–] the_doktor@lemmy.zip 3 points 3 months ago* (last edited 3 months ago) (2 children)

Working in computing for years and this is what I've heard

2000: IPv4 is about to dry up, we really need to start moving to v6!

2005: OH NO THE SKY IS FALLING IPv4 IS ALMOST GONE! IPv6 IN THE NEXT YEAR OR TWO OR THE INTERNET WILL DIE!

2010: WE'RE SERIOUS THIS TIME IPv6 NEEDS TO BE A THING RIGHT NOW! HELP!

2015: Yeah, okay, NAT has served us well so far, but we can only take it so far, we really need v6 to be the standard in the next 5-10 years or we're in trouble!

2020: Um... guys? IPv6? Hello? Anyone? crickets

2024: IPv6ers are now the vegans of networking

this may or may not be satire, just laugh if unsure

[–] Aux@lemmy.world 1 points 3 months ago

IPv4 dried up a long time ago. But it's different for every country. Countries like US and UK simply took over large blocks of IPv4 addresses and countries like Brazil got fucked. So, if you're in a country with a large pool, you won't notice any issues today, but if you're not so lucky, a lot of internet services are not accessible to you because some dickhead got IP banned and that IP is shared by thousands if not millions of users in your country.

[–] MystikIncarnate@lemmy.ca 1 points 3 months ago (2 children)

As a networker, ipv6 is the future. I'm a fan of it, but I don't really talk about it anymore because there's no point.

I threw in the towel after an ISP messed up so badly that I just couldn't bother anymore.

At a previous job a client I was doing some work for got a new internet connection at a new site, the ISP ran brand new fiber for it. This wasn't a new building or anything, but the fiber was new. They allocated them a static IPv4 thing as usual, and I asked the tech about V6, and they said we would have to take it up with the planning team, so I did. I was involved in the email chain at the end of the sales process to coordinate the hookup. So I asked. After many emails back and forth, I was informed the connection was allocated.

They allocated one single IPv6 subnet directly off of their device. I couldn't even.

For those that don't understand, the firewall we had connected to the device is an ipv6 router. What normally happens, especially in DHCP customer connections, is that the router will use DHCP-PD to allocate a subnet for the router to use on the LAN, and automatically set up a route to say "reach this subnet we allocated for this router, via this router" kind of thing. I'm dramatically simplifying, but that's the gist. In DHCP-PD, the router will also have an IPv6 address on the ISP-facing link to facilitate the connection. In the case of the earlier story, they gave us an entire subnet to communicate between the ISP and the router, and didn't give us a subnet for the client systems inside the network.

I did ask about this and I can only describe their reply as "visible confusion".

I know many who will still be confused by this point are people who have not used IPv6; to explain further: the IP on your local (LAN) systems needs to be a public IP address, because the router no longer does network address translation when sending your data to the internet. So the IP on the router has no bearing on your computer having a connection to the internet over v6. If your local computer does not have a globally unique ipv6 address, you cannot use IPv6. There are ways around this, NAT66 exists but it's incredibly bad practice in most cases. The firewall I was working with didn't really support NAT66 (at least, at the time) and I wasn't really going to set that up.

ISPs are the reason I gave up on IPv6.

I'll add this other story to reinforce it. I'll keep it brief. A different ISP for a different company at a different site entirely. The client purchased a static IPv4 address, and I asked about IPv6, as you do. To preface, I know this company and used them for my own connection at the time. They have IPv6 for residential clients via DHCP-PD. I was told, no joke, that because of the static IPv4 assignment, and how they execute that for businesses, that they couldn't add IPv6 to the connection, at all.

The last thing I want to mention is a video I saw, which is aptly named "CGN, a driver for IPv6 adoption" or something similar. It's a short lecture about the evils of carrier grade NAT, and how IPv6 actually fixes pretty much all the bs that goes with CGN, with fewer requirements and less overhead.

IPv6 is coming. You will prefer IPv4 until you understand how horrific CGN is.

[–] Disaster@sh.itjust.works 1 points 3 months ago

CGnat is an abomination.

[–] the_doktor@lemmy.zip 0 points 3 months ago (1 children)

Yep. It was mostly a joke. Mostly. The bungled adoption of v6 plus all the ways we can still leverage v4 is what's keeping v6 from being adopted any time soon, but one day we're going to have to rip off the band-aid and just go for it. Sure, v6 is going to bring its own issues and weirdness, but FUTURE!

[–] Hobo@lemmy.world 0 points 3 months ago* (last edited 3 months ago) (2 children)

I swear it's going to be a generational change where it takes a slow adoption by the younger network people as the older network people slowly retire. Kind of like how racism and sexism has diminished. It wasn't like we changed anyone's mind, just that people held onto it until they died and younger people just said, "The future is now, old man." and moved past it.

[–] MystikIncarnate@lemmy.ca 0 points 3 months ago (1 children)

All I want to say about this is that the technology specialists, especially in networking, are usually not this opposed to change. Things change for networking and systems folks all the time. We're used to it. Most of the time the hard sell is with the management folks who Green light projects. They don't want to "waste" money on something that "nobody wants".

Legitimately, one company I asked about IPv6 said to me that customers had not requested it, so they haven't spent any time on implementing it.

As if customers know what's good for them....

[–] crispy_kilt@feddit.de 0 points 3 months ago

I see you've worked with my employer

[–] Semi_Hemi_Demigod@lemmy.world 0 points 3 months ago (1 children)

"IP address are four sets of numbers with dots in between AND THAT'S HOW I LIKES IT!" - Me, an old network guy

Honestly the fact that I can't remember or type IPv6 addresses is a big reason I haven't bothered figuring it out.

[–] crispy_kilt@feddit.de 0 points 3 months ago

That's not what an IP is though, that's just dotted representation

[–] chris@l.roofo.cc 1 points 3 months ago (1 children)

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.....

[–] drkt@lemmy.dbzer0.com 0 points 3 months ago* (last edited 3 months ago) (1 children)

Yes but IPv4 is becoming expensive and it's annoying having to use a middleman to clone github repos on a v6-only VPS

IPv6 is not hard, there is no excuse not to have it

[–] 30p87@feddit.de 0 points 3 months ago (1 children)

Or one could use alternative hosters, or maybe even selfhost git services.

[–] drkt@lemmy.dbzer0.com 0 points 3 months ago (1 children)

Yeah let me self-host other peoples github repos because github doesn't have IPv6 lmao dude

[–] 30p87@feddit.de 0 points 3 months ago

How about "Let me selfhost my own repos, so other people working with my stuff can use IPv6, as well as be sure no large corporation known for being cancer stands behind it and monitors every thing I do."?

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

[–] bigredcar@lemmy.world 1 points 3 months 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.

[–] starman@programming.dev 0 points 3 months ago (1 children)

How do you guys remember IPv6 addresses?

[–] bfg9k@lemmy.world 1 points 3 months 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

[–] Heavybell@lemmy.world 0 points 3 months ago

I would like to use IPv6 but google and MS are having a dick waving contest with competing implementations, as I understand it. So fuck it.

[–] henfredemars@infosec.pub 0 points 3 months ago* (last edited 3 months ago) (1 children)

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.

[–] skilltheamps@feddit.de 0 points 3 months 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.

[–] computerscientistII@lemm.ee -1 points 3 months ago (1 children)

Retardistan is hogging the biggest portion of the IPv4 addresses for themselves. That's why they have the worst IPv6 support. The need arose last in this part of the world.

[–] JackbyDev@programming.dev 0 points 3 months ago (1 children)
[–] crispy_kilt@feddit.de 0 points 3 months ago

I think he means the USA

[–] GTG3000@programming.dev -1 points 3 months 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.

[–] ngn@lemy.lol -1 points 3 months ago

whats the problem with IPv4?

[–] RecluseRamble@lemmy.dbzer0.com -1 points 3 months ago* (last edited 3 months 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.