Hello, I can confirm this. When we determine "the address" of the probe for both IPv4 and IPv6 the connection address has top priority of course. But after that, for IPv4 we prefer the ip-echo, for IPv6 we prefer the local address. That works mostly, but not when you use ULA (only). We can consider this to be a bug; we'll fix it. Thank you for reporting, Robert On Wed, Oct 23, 2024 at 12:22 AM Matteo Bonora <matteo@bonora.eu> wrote:

Hello everyone,

maybe it's me that I have an unusual configuration, but I was wondering if any of you are experiencing the same behavior...

For IPv6 I use in my local network an ULA prefix, to maintain an abstraction layer between my network and the IPv6 prefixes assigned by my ISPs.

Each ULA address of any of my devices gets translated via NPTv6 by my router to a global address compatible with my ISP assigned prefix.

My probe as well has an ULA address and a public/global address that gets correctly detected by Atlas servers via IP Echo Service, but is the wrong IP that gets elected as the reference address within the Probe Address Discovery section. The correct one should come from IP Echo Service, but the ULA seems to be the preferred one.

[image: 2024-10-23_00h07_14.png]

Any ideas? Is there a way to force the selection of the IP Echo one?

Thanks

Matteo

----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/