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

Does that mean they are assigning random IPv6 addresses to computers on the network for each peer or connection and maintaining a mapping in memory?


Normal static address is assigned. Whether it comes from the external range or from the link-local range doesn't really matter. You could potentially randomise the source at the exit to prevent identification of your hosts, but you don't have to.

For most practical cases just imagine you're getting a big ipv4 range. Whatever you can do with it - you can do the same with ipv6. NAT, no NAT, filtering, static or dynamic assignment.


That's what I'm asking. IPv6 feels like a regressiin over NATv4 because it can leak which internal device made a request. Is there a standard way to randomize addresses that works with ofd-the-shelf router firmware. Also, are link-local IPv6 leaking MAC addresses?


Yes, there is a standard since about 10 years ago. It's not dependent on your router firmware, in accordance with IP's end-to-end design philosophy (keep the network dumb, and hosts smart). Here's some links to get you started:

https://slaptijack.com/networking/osx-disable-ipv6-address-p...

http://andatche.com/blog/2012/02/disabling-rfc4941-ipv6-priv...

As for link-local IPv6 addresses, those aren't even accepted by the socket API[1] in place of normal routable addresses. They're only used for low level things like neighbour discovery (IPv6 equivalent of ARP) and apps that go out of their way to use them. They aren't routable outside your L2 segment.

[1] as in:

   $ telnet fe80::something:something:42
   Trying fe80::something:something:42...
   telnet: Unable to connect to remote host: Invalid argument




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

Search: