Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Suffix should always be static with SLAAC because it’s your MAC address. Even if you’re using privacy extensions (and you should) you should still be able listen on the MAC address one.

If you’re using DHCPv6 then the DHCP server should take care of DNS as it would for v4.



> Suffix should always be static with SLAAC because it’s your MAC address.

Except for devices that randomize mac addresses. Normally even those that do that only try do so when connecting to a new network but that's not always reliable.

> Even if you’re using privacy extensions (and you should) you should still be able listen on the MAC address one.

I'm doubtful that all applications make that distinction and advertise the right address. If they just use some external "what is my IP" service to determine their address because that's what they did for IPv4 then they'll get the privacy address and advertise that to peers because that'll be picked by default for outgoing connections.

Being able to allow incoming connections to a port for any address belonging to a particular machine would be less error-prone.


These issues will keep happening, in completely unrelated domains, as long there are not fines for violating security best practices.


AFAIK the goal is to get rid of MAC adresses entirely - so how is this going to work?


I don’t think that is the goal, no.


There was always a tension between the Internet and Ethernet guys, the Internet guys have won, so Ethernet-specific concept like MAC adresses are on their way out ?


Not at all - MAC is layer 2, IP is layer 3.


Yes, and the two layers are represented by different political groups, each of which is trying to dominate.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: