Timeline for Two ULA addresses on one interface
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2023 at 17:06 | comment | added | Cpt.Whale | 1) yes, I should have said 'through' the gateway. 2) yes, it's the slaac template from which to generate privacy addresses. 3) It was a generalization/simplification on my part. The slaac IPs can come from autoconfiguration with other devices on the network, and just get used for local traffic (but can be routable + advertised from the router). A dhcpv6 address will come from your router and get a route out. You can use both though, but the actual rules for which gets used when depend more on your client's OS/network stack/routing table. I'm not familiar enough to go into much detail there | |
| Dec 7, 2023 at 8:22 | comment | added | NickG | 1) "and the /128 address to communicate directly with the gateway": I've seen that in order to communicate with the router, the link local address is also used. Do you mean it will use this address when needed to be routed outside the LAN? 2) About the mngtmpaddr flag: Is this related to creating the IID for the SLAAC ULA address not as an EUI-64 but with a hash function, to avoid privacy issues? 3) Is there a reason why the SLAAC ULA addr is used on the LAN and the DHCP one is used for the gateway? I guess both ULAs could work in both cases? | |
| Dec 4, 2023 at 22:24 | history | answered | Cpt.Whale | CC BY-SA 4.0 |