Hacker News new | ask | show | jobs
by Galanwe 54 days ago
> I'm not sure what you mean by "fix" DHCP

SLAAC was part of IPv6 since the original RFC, its a horribly over engineered stateless replacement of DHCP. Nobody asked for that.
2 comments
simoncion 54 days ago
> Nobody asked for that.

I wasn't around for the discussions at the time, but I would have asked for it if I was. SLAAC is IPv4LL, except that you usually get a globally-routable IP address from it. It's great. It's also quite a bit simpler than DHCP... "If the advertised prefix permits autonomous addressing, generate a host part in the non-fixed part of the prefix, run DAD on the generated address to ensure it's not in use, and start using it if it's not.".

> SLAAC was part of IPv6 since the original RFC...

An attentive reader notices that RFC 1883 and RFC 1971 are separated by nearly a year.

link
KaiserPro 54 days ago
> Nobody asked for that.

I mean thats not true. SLAAC is great for public/untrusted networks where you just let the clients figure that shit out.

the only thing thats a bummer is not being able to map DNS records to addresses, which is kinda the point, for privacy.

link
kazen44 54 days ago
this is still kind of possible, by doing neighbour discovery and querying the host for its hostname with mdns.

In my opinion, this automatic mapping of DNS names to addresess is not part of the IP protocol, and shouldn't be.

link
simoncion 53 days ago
> ...mdns

"use MDNS for name resolution" works until your machine is reattached to your LAN and your MDNS server thinks your hostname is "in use" and sticks a "-N" at the end of it to "avoid hostname collisions". Though, it might just be Avahi that has this particular bit of brain damage... I haven't paid attention to the behavior of the Macs that I've been obligated to use over the years.

Few people are more sad about this behavior than I am.

link