networking

2824 readers

2 users here now

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

founded 1 year ago

MODERATORS

[email protected]

[Question] what exactly is hard about adopting IPv6?? (self.networking)

submitted 5 months ago by danhab99 to c/[email protected]

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

[–] [email protected] 1 points 5 months ago

What about it is fiddly?

The insane addresses. The reliance on DNS, the unpredictability of addresses, that each device can have so many addresses and you need to know what each does and is used for and how that impacts inter-network routing and firewall rules. Privacy IPs, what the hell? Its a solution to something that's fixed by tried and understood IPv4 NAT.

If you just want a flat simple network where everything on your lan is equal, everything has a globally unique and trackable IP I'm sure it's fine. But if you have something more sophisticated it becomes much more complicated. And I genuinely can't see how IPv6 advocates can't see the problems it introduces.

What we need is a larger address space and fast adoption, that's it. If after 30 years of awful adoption rates and only when people have a gun to their head they begrudgingly might adopt it, then you have a bad protocol.