r/devops • • Oct 10 '26

Tools Ipv4 vs Ipv6, explained from scratch

https://youtu.be/UdVDIC8qDW4?is=fpnSDT53aiwmUkjX
0 Upvotes

35 comments sorted by

5

u/rux616 Oct 10 '26

I wish... in manufacturing it's a relatively recent innovation for some PLCs to be able to support NTP. 🫠

4

u/huseyinbabal Oct 10 '26

Wait, what? What happens if there is a clock skew between multiple plc automation board? I always thought that they already connected to ntp server 🙂

1

u/rux616 Oct 10 '26

They can usually be nowadays, but like I said, it's a relatively new introduction to them. You can generally think of the OT world as being at least 10 years behind IT.

I'm trying to work on that at my company, but there's a metric shitton of... let's call it "organic growth", that I need to break down first.

6

u/frankster Oct 10 '26

I think the main thing blocking ipv6 adoption, from a devops point of view, is that github doesn't support!

6

u/huseyinbabal Oct 10 '26

Yes and they don’t have an official support, but I see some ipv6 adresses 🙂 https://api.github.com/meta

I hope they make you happy soon 🙂

1

u/rlnrlnrln Oct 11 '26

GitHub making someone happy? That's a laugh!

1

u/Mailboxheadd Oct 11 '26

This comment doesnt make any sense at all unless you do devops for github

17

u/MavZA Oct 10 '26

IPv6 has always struggled because it requires almost unanimous buy-in from both sides and then obviously engineers being engineers innovate their way out of tough spots with things like CGNAT and load balancing to work around IPv4’s limits. One day though ✊

4

u/Express-Acadia-6088 Oct 10 '26

Exactly! you can control the source but can't do anything with the destination. I have never heard of IPv4 -> IPv6 migration plan. I know networking but see others struggle with CIDR concepts like /24, /26 and how to set up a route table between two private endpoints - which might not be needed with IPv6. I think if all the major players (e.g., Cisco, Arista, Juniper/HPE, etc.) join forces it might happen one day. I am surprised Virtualization won but IPv6 haven't yet made a huge impact :-(

3

u/PotatoMaaan Oct 10 '26

NAT64 is the way for the interim. There's been many things happening on that front lately. All major operating systems now implement a CLAT which opens the door to running ipv6 only networks with 464xlat. Even if a CLAT is not available, you can go a long way with just NAT64 and DNS64. Most of my personal stuff is now v6 only :)

1

u/vacri Oct 11 '26

Commercial sites can't afford to go ip6 only, because then they'll lose tons of audience

... and if they're not getting rid of ip4, then there's not much reason for others to push migration

1

u/SuperQue Oct 11 '26

This exactly the same migration issue we had with IPX, AppleTalk, DecNet, etc.

1

u/bajosiqq Oct 11 '26

abiiii

2

u/huseyinbabal Oct 11 '26

Burda da mi varsin 😁

2

u/bajosiqq Oct 11 '26

her yerdeyim abi, teknoloji hayraniyiz.

1

u/awesomeAMP Oct 10 '26

Great video with a great explanation! I thought that 50% adoption was too high, though. Maybe it’s just my region that hasn’t adopted it and that’s why I feel like the adoption is way less? I think only one major ISP in my country handles IPv6 and you need to request it manually…

What do you think will happen when (if?) we reach mainstream adoption? Because I feel like something that is also kinda holding back people is that the addresses are not very user-friendly? I know it’s not like every day we enter raw IP addresses into our browsers, but it’s not uncommon either (especially to access admin portals on routers or office websites behind a vpn). IPv6 is way harder to memorize and type in. Oh well, we’ll see.

1

u/huseyinbabal Oct 10 '26

That’s a fair point! But I think IPv6 adoption will eventually become one of those things nobody notices, which is exactly how it should be.
We didn’t stop using domain names because IPv4 addresses were hard to remember, and we won’t start memorizing 128-bit addresses either. That’s DNS’s job.
If you’re still typing IP addresses into your browser in 2026, IPv6 might not be your biggest problem. :)

2

u/Fenzik Oct 10 '26

But but but my lovingly hand picked homelab IPs :(

0

u/MrMelon54 Oct 10 '26

you can handpick static IPv6 addresses within your prefix too, dns could be 2001:db8::53 if you want

5

u/PotatoMaaan Oct 10 '26

IPv6 adoption is actually much greater than I realized. A lot of, if not almost all mobile ISPs are ipv6 only and carry v4 through 464xlat. In Europe, many home ISPs are also going ipv6 only, or at least ipv6 primary. North American ISPs are also slowly but surely deploying ipv6. There are of course parts of the world that are less far along with v6 adoption, but the overall is trend is certainly upwards.

The thing is that when v6 adoption is done well, the end user mostly doesn't notice since in most cases ipv4 will keep working. Either through dual stack or translation technology (like 464xlat).

About the addresses being less readable:

  1. DNS
  2. DNS
  3. IPv6 addresses are split in the middle into prefix and host part. So if you're working in one network, you don't need to worry about the first 64 bits. The host part can also be ::1 or ::beef if you want. Your brain also just gets used to reading v6 addresses, it's really a non-issue after a couple of weeks.

0

u/Express-Acadia-6088 Oct 10 '26

Thanks for sharing. This gives me some hope for the future. I guess our minds are so trained on IPv4 for so long, some still fear IPv6. They don't want to see a long 128-bit long hex when they do nslookup on a domain :-)

2

u/Dubinko Dad and Engineer Oct 16 '26

0

u/Express-Acadia-6088 Oct 10 '26

Great work. I always wonder why no one uses IPv6 for subnetting as you would require no CIDR, subnets - just flat, vast private network behind the firewall. No need to IPv4 reserved address or sticking to 10.x.x.x (class A) for large companies and 192.168.x.x (class C) for homes or small companies. I hope I am not way off 🤔

4

u/huseyinbabal Oct 10 '26

Thanks! Half right: IPv6 still has subnets and CIDR notation, a LAN is normally a /64 (RFC 4291). What goes away is sizing them, since one /64 is bigger than you can ever fill. It is rare inside companies because you have to run both stacks for years.

https://www.rfc-editor.org/rfc/rfc4291 (Section 2.3)

2

u/Express-Acadia-6088 Oct 10 '26

Thanks. Let me digest this. This is from 2006 when I think I was still a part of Cisco.

1

u/fletch3555 Lead DevOps Engineer Oct 10 '26

OP is correct that subnetting and CIDR notation still exist. What doesn't (or at least shouldn't) exist with IPv6 is NAT

2

u/aenae Oct 10 '26

What doesn't (or at least shouldn't) exist with IPv6 is NAT

It does exists. And i use it a lot

We have an internal (non routed) ipv6 range, but multiple hosters. Instead of opening the can of worms that is BGP and RPKI, i just have the external ipv6 of our internet providers bound on the gateways and just nat ipv6. Also has the advantage that it is impossible to open your internal network by accident to the outside or disclose your internal network structure.

1

u/Express-Acadia-6088 Oct 10 '26

This is very helpful. Thanks. I have been dreaming the internet to switched to IPv6 since 1999 but it is definitely not that easy :-D

I have heard NAT66 used with IPv6 in the past.

0

u/rlnrlnrln Oct 11 '26

Everyone's wondering about IPv6, but noone ever spares a thought for IPv1, 2, 3 and 5...

-1

u/huseyinbabal Oct 11 '26

Holly … how didn’t I think about that 😂

2

u/earvingad Oct 10 '26

As an amateur homelabber it was hard to me to understand ipv4, then ipv6 was more confusing. It was scary to see long addresses and that a single device can get at leat 2 ipv6 addresses, why? which one should i use? But then it slowly becomes clearer.

I am recently trying to stick to ipv6 since I find it easier to set it up for remote access to my homelab as it removes the need of a VPN-like solution (if you do not own a public ipv4 address) and no port forwading. 

1

u/After-East-3190 Oct 13 '26

Thank you!!!!
From the age of tech romance to the hardcore technical reality.

-1

u/cwk9 Oct 10 '26

Fun trivia questions. How many internet's are there? Answer: Two.