networking

2811 readers

1 users here now

Community for discussing enterprise networks and the ensuing chaos that comes after inheriting or building one.

founded 1 year ago

MODERATORS

manifex@sh.itjust.works

[Question] what exactly is hard about adopting IPv6?? (programming.dev)

submitted 4 months ago by danhab99@programming.dev to c/networking@sh.itjust.works

17 comments fedilink hide all child comments

I mean on a technical level. Are the devices that make up the infrastructure of the internet hardwired with IPv4? Is the firmware on these devices impossible to upgrade remotely?

If it's just a matter of software or firmware then adoption should only take like a year but clearly that isn't the case. So what specifically is stopping us?

you are viewing a single comment's thread
view the rest of the comments

[–] Max_P@lemmy.max-p.me 13 points 4 months ago

Everyone's making money on IPv4, so there isn't the incentive just yet to really switch or invest in even supporting it. Major clouds now charge per IP, residential ISPs are starting to make having a public IP a feature they charge extra for otherwise you get CGNAT, mobile carriers don't want people to host stuff and are quite happy with CGNAT.

And then there's the implementation part where everyone seems to go out of their way to do it wrong and cause trouble. My OVH server for example assigns me a non-routed /56 and I can only use about 8 of them before their router starts ignoring the rest.

At home I have to do 6rd over PPPoE over VLAN which causes my router to not be able to do hardware accelerated routing and I lose 3/4 of my connection speed on top of the resulting tiny MTU, and it turns out IPv6 doesn't like that. And then a few days later their 6rd endpoint changes and your connection dies until restarted manually, and somehow you end up with another IPv6 block and ugh it's just so horribly broken.

I want IPv6 to work but damn, ISPs aren't making it easy to adopt it in the first place.