This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] ULA detected by probe?
- Previous message (by thread): [atlas] ULA detected by probe?
- Next message (by thread): [atlas] Problem with new Openipmap
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Wed Dec 6 11:24:11 CET 2017
Hi Jordi, On 2017/12/02 10:41 , JORDI PALET MARTINEZ wrote: > And > Addresses fd3f:4830:fd21:0:220:4aff:febf:ffaf/64 > 2001:…. I'm not aware of any case where an Atlas probe created an IPv6 ULA out of thin air. Addresses are either statically configured or derived from a prefix in a router advertisement. So most likely the probe picked it up from an RA. Your probe is now up for 27 days. So that's the time period where the probe could have received the RA. If the lifetime in the RA is infinite, then the prefix will essentially stay there forever, or until another RA modifies the lifetime. > How is that possible and how to clean up it? The easiest way to get rid of it is to powercycle the probe. Philip
- Previous message (by thread): [atlas] ULA detected by probe?
- Next message (by thread): [atlas] Problem with new Openipmap
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]