Am 21.06.21 um 08:20 schrieb Marco Davids (IETF) via ripe-atlas:
Hi,
Whenever my network get's a different IPv6-prefix from my provider (which happens every now and then), the probe is flagged down in the dashboard.
The reason seems to be that RIPE Atlas probes are unable to renew their (SLAAC?) IPv6-addresses when needed. Only solution is a powercycle.
Is this a flaw, or is it by design?
I have had similar problems - even if I change a probe quickly between different LANs/ISPs. I assume you talk about a hardware probe (the behavior on software probes is out of control of ripe). Recognizing the new network takes a while. But in the end, I think it is a flaw of your router. It should withdraw the old prefix by using reasonable life times/ zero life times. Here is an example with a hw probe and ~daily reconnects. The measured disconnected time is between 2 and 5 minutes usually. I think that's ok. https://atlas.ripe.net/probes/53236/#tab-network Regards, Thomas