Hello,
On 15/10/20 07:27, Henrik Friedrichsen wrote:
Hey,
On Wed, Oct 14, 2020 at 02:30:04PM -0300, Fernando Gont wrote:
And you may also look at this other one, which has recommendations for CPEs,
which in your case accounts for your DHCPv6-PD and RA daemons:
https://tools.ietf.org/html/draft-ietf-v6ops-cpe-slaac-renum-05
Looks like it's a problem that's not (easily) solved yet.
Agreed.
Thanks for the suggestions everyone. I'll reduce the lifetimes to the numbers
suggested in the draft and move the reconnect to 5am as suggested by Stuart.
Can this cause problems for connections that exceed these lifetimes?
No. Because the RAs are expected to refresh the associated timers.
(i.e., if you set the Preferred Lifetiem to 15 minteus and the Valid
Lifetime to 30, the idea is that hosts might receive one unsolicited RA
every, say, 5 minutes... and these RAs would refresh the associated
timers and wouldn't let them expire).
It seems
that at least macOS will assign a new IPv6 address with every advertisement due
to privacy extensions.
Could you doublecheck? That'd be a bug.
I'd hope that existing sockets will remain connected if
the advertised prefix doesn't change, but I'm not sure.
Indeed. As long as the Prefix doesn't become invalid, the sockets would
remain unaffected.
Thanks,
--
Fernando Gont
e-mail: ferna...@gont.com.ar || fg...@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
