You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Infinite lifetimes mean these ULA addresses never expire on a host and will always be considered valid source and destination addresses during RFC6724 source and destination address selection.
One consequence is that a mobile device that has a high uptime (e.g. a smartphone), moves between a number of IPv6 networks, and uses IPv6 privacy addresses, could end up with a lot of unusable ULA addresses on its network interface. They may accumulate continuously until the device is rebooted.
The text was updated successfully, but these errors were encountered:
This behavior can be changed by setting ra_useleasetime to 1; in this case odhcpd will take the smallest value of either the leasetime or the valid lifetime of an IPv6 address
I'm guessing it might be referring to the IPv6 Global Unicast Address (GUA) delegated prefix lease time learned via DHCPv6-PD.
This lease time isn't relevant to the Unique Local Address (ULA) prefix, as the that is a local network only prefix who's existence and lifetimes are independent of a GUA delegated prefix, and independent of whether a GUA prefix has been supplied or not by the ISP.
markzzzsmith:
Supply the following if possible:
IPv6 enabled by default, OpenWRT automatically generates a unique ULA prefix per RFC4193.
ULA prefix is announced with Infinite Preferred and Valid Lifetimes, rather than the RFC4861 defaults:
AdvPreferredLifetime: Default: 604800 seconds (7 days)
AdvValidLifetime: Default: 2592000 seconds (30 days)
e.g., using the 'rdisc6' utility to display RAs:
[root@opy mark]# rdisc6 wlp3s0
Soliciting ff02::2 (ff02::2) on wlp3s0...
[...]
Prefix : fdec:91f6:8c3a::/64
On-link : Yes
Autonomous address conf.: Yes
Valid time : infinite (0xffffffff)
Pref. time : infinite (0xffffffff)
[...]
Infinite lifetimes mean these ULA addresses never expire on a host and will always be considered valid source and destination addresses during RFC6724 source and destination address selection.
One consequence is that a mobile device that has a high uptime (e.g. a smartphone), moves between a number of IPv6 networks, and uses IPv6 privacy addresses, could end up with a lot of unusable ULA addresses on its network interface. They may accumulate continuously until the device is rebooted.
The text was updated successfully, but these errors were encountered: