Agreed. Though I wonder if ipv6 will ever displace ipv4 in things like virtual networks (docker, vpn, etc.) where there's no need for a bigger address space

[–] captainjaneway@lemmy.world 28 points 4 months ago

I hope so. I don't want to manage two different address spaces in my head. I prefer if one standard is just the standard.

[–] domi@lemmy.secnd.me 28 points 4 months ago

Yes, because Docker becomes significantly more powerful once every container has a different publicly addressable IP.

Altough IPv6 support in Docker is still lacking in some areas right now, so add that to the long list of IPv6 migration todos.

[–] jlh@lemmy.jlh.name 19 points 4 months ago* (last edited 4 months ago)

I'm using IPv6 on Kubernetes and it's amazing. Every Pod has its own global IP address. There is no NAT and no giant ARP routing table slowing down the other computers on my network. Each of my nodes announces a /112 for itself to my router, allowing it to give addresses to over 65k pods. There is no feasible limit to the amount of IP addresses I could assign to my containers and load balancers, and no routing overhead. I have no need for port forwarding on my router or worrying about dynamic IPs, since I just have a /80 block with no firewall that I assign to my public facing load balancers.

Of course, I only have around 300 pods on my cluster, and realistically, it's not really possible for there to be over 1 million containers in current kubernetes clusters, due to other limitations. But it is still a huge upgrade in reducing overhead and complexity, and increasing scale.

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

I wish everything would just default to a unix socket in /run, with only nginx managing http and stream reverse sockets.

[–] verstra@programming.dev 4 points 4 months ago (1 children)

Wait, but if you have, for example an HTTP API and you listen on a unix socket in for incoming requests, this is quite a lot of overhead in parsing HTTP headers. It is not much, but also cannot be the recommended solution on how to do network applications.

[–] WaterWaiver@aussie.zone 1 points 4 months ago

Replacing a TCP socket with a UNIX socket doesn't affect the amount of headers you have to parse.

[–] vk6flab@lemmy.radio 6 points 4 months ago

It's not real.

[–] PenisWenisGenius@lemmynsfw.com 4 points 4 months ago* (last edited 4 months ago)

I use ipv6 when possible but it's rarely possible. I've never had home internet that was ipv6 ready enough for my wan address when googling "what's my ip" to be something besides an ipv4 number.

Could I get ipv6 over otherwise non ipv6 compatible hardware using a vpn?

[–] 0x0@programming.dev -1 points 4 months ago (1 children)

we’ve been out of IPv4 for over a decade now

Really? Haven't had trouble allocating new VPSs with IPv4 as of late...

[–] frezik@midwest.social 7 points 4 months ago

You're probably in a country that got a ton of allocations in the 90s. If you came from a country that was a little late to build out their infrastructure, or even tried to setup a new ISP in just about any country, you would have a much harder time.