Shorten the lifetime of IPv6 prefixes announced by radvdThis helps when the prefix is dynamic (allocated by ISP dynamically, for example).
See also: radvd.conf(5) – Linux man page
123456789 interface br0{ prefix ::/64 { # ... other stuffs AdvValidLifetime 300; # The length of time in seconds that the prefix is valid for the purpose of on-link determination AdvPreferredLifetime 120; # The length of time in seconds that addresses generated from the prefix via stateless address autoconfiguration remain preferred. };};
According to the man page above, AdvValidLifetime less than 2 hour could be ignored for existing prefix. But that’s not the case here as this option also applies on the prefixes newly obtained by the router. Hence it’s applied the first time the prefix is announced on LAN. RFC 4862/5.5.3.e-1 also confirms this by “If the received Valid Lifetime is greater than 2 hours or greater than RemainingLifetime“.
After apply these options, my clients now discard the old prefix more timely.
This helps when the prefix is dynamic (allocated by ISP dynamically, for example).
See also: radvd.conf(5) – Linux man page
1 2 3 4 5 6 7 8 9 | interface br0 { prefix ::/64 { # ... other stuffs AdvValidLifetime 300; # The length of time in seconds that the prefix is valid for the purpose of on-link determination AdvPreferredLifetime 120; # The length of time in seconds that addresses generated from the prefix via stateless address autoconfiguration remain preferred. }; }; |
According to the man page above, AdvValidLifetime less than 2 hour could be ignored for existing prefix. But that’s not the case here as this option also applies on the prefixes newly obtained by the router. Hence it’s applied the first time the prefix is announced on LAN. RFC 4862/5.5.3.e-1 also confirms this by “If the received Valid Lifetime is greater than 2 hours or greater than RemainingLifetime“.
After apply these options, my clients now discard the old prefix more timely.