News for hackers. Stuff that matters.

A comment on Reclaiming IPv4 Class E's 240.0.0.0/4. Parent comment

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by baq on Monday May 27, 2024 @12:43PM (#40492403)
It should be deployed everywhere where IPv6 is deployed and there's an IT department if only for logging/audit.
[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by kccqzy on Monday May 27, 2024 @01:01PM (#40492573)
Stateful DHCPv6 does not get deployed because IPv6 purists at Google refuse to implement them on Android. And I in fact agree with them.

And DHCPv6 isn't needed for logging/audit: the router always has an association of MAC addresses and IPv6 addresses even if hosts assign their own addresses with SLAAC.

[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by bigstrat2003 on Tuesday May 28, 2024 @02:13PM (#40503701)
> Stateful DHCPv6 does not get deployed because IPv6 purists at Google refuse to implement them on Android.

Which is absolutely ridiculous. Google should not be trying to dictate to their customers how to run infrastructure. If someone wants to use stateful DHCPv6 for their Android devices, that is their right and Google has no business standing in their way.

[ Parent | on HN ]
Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by jandrese on Tuesday May 28, 2024 @01:08AM (#40497499)
IPv6 DHCP isn't the same as IPv4 DHCP though. It doesn't work very well for logging and audits. It's more for assigning prefixs to routers.
[ Parent | on HN ]