I just joined the RIPE-Atlas fold with probe #35105 and am still learning the ropes. My public-facing internet servers are all IPv6-only. That means that the only meaningful measurements of my systems come from IPv6 capable probes. I was surprised to see that IPv4-only probes would be scheduled to send IPv6 pings, traceroutes, nslookups etc. Even when I added "system: IPv6 Works" to the include tags and "system: IPv6 Doesn't Work" to the exclude tags I still got some IPv4-only probes assigned. Are those tags for future use and not wired up yet? Are the IPv4-only probes I'm seeing in my test runs there because their status changed recently and previously they were IPv6 capable?  -wolfgang
Hi Wolfgang, welcome to the community! On 28/01/2018 01:20, Wolfgang S Rupprecht wrote:
I was surprised to see that IPv4-only probes would be scheduled to send IPv6 pings, traceroutes, nslookups etc. Even when I added "system: IPv6 Works" to the include tags and "system: IPv6 Doesn't Work" to the exclude tags I still got some IPv4-only probes assigned. Are those tags for future use and not wired up yet? Are the IPv4-only probes I'm seeing in my test runs there because their status changed recently and previously they were IPv6 capable?
These tags are currently reapplied every 4 hours, so there is indeed the possibility that a probe is no longer capable of carrying out measurements with a particular address family even though it has an "IPvX Works" tag applied. If you have a particular example or examples then please send them to me directly and I will take a look to see if there's anything strange going on. Regards, Chris Amin RIPE NCC
participants (2)
-
Chris Amin -
Wolfgang S Rupprecht