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] Probe questions - reporting clearly busticated probe configs?
- Previous message (by thread): [atlas] Probe questions - reporting clearly busticated probe configs?
- Next message (by thread): [atlas] Probe questions - reporting clearly busticated probe configs?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Amin
camin at ripe.net
Fri Jan 18 11:40:42 CET 2019
Hi Christopher, On 16/01/2019 20:18, Christopher Morrow wrote: > > hey wait.... The first of my examples: > https://atlas.ripe.net/probes/26725/#!tab-general > <https://atlas.ripe.net/probes/26725/#%21tab-general> > > has: > System TagsV3 Resolves A Correctly Resolves AAAA Correctly IPv4 Works > IPv6 Works IPv4 Capable IPv6 Capable IPv4 RFC1918 IPv4 Stable 90d > > suspiciously: "system-ipv6-works" is in that list... even though the v6 > address is: > 2001:db8:4447:0:eade:27ff:fec9:7134/64 This probe has the "system-ipv6-works" tag because it can successfully ping at least one IPv6 target. You can see at https://atlas.ripe.net/probes/26725/#!tab-builtins that it can in fact reach a number of IPv6 targets. Note that the probe host for 26725 has tagged the probe as "IPv6NAT", maybe this explains the discrepancy you are seeing? Regards, Another Christopher
- Previous message (by thread): [atlas] Probe questions - reporting clearly busticated probe configs?
- Next message (by thread): [atlas] Probe questions - reporting clearly busticated probe configs?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]