Re: [atlas] check dns64/nat64 behavior ?

2020-02-21 Thread Philip Homburg
On 2020/02/21 14:50 , Thomas Schäfer wrote: > Am 21.02.20 um 14:38 schrieb Thomas Schäfer: >> Hi, >> >> is there a simple way to check the reachability of IPv6 targets by >> probes behind NAT64? > > IPv4 targets of course. On NAT64, an IPv4 address is accessed over IPv6. You do need to disable th

Re: [atlas] check dns64/nat64 behavior ?

2020-02-21 Thread Thomas Schäfer
Am 21.02.20 um 14:38 schrieb Thomas Schäfer: Hi, is there a simple way to check the reachability of IPv6 targets by probes behind NAT64? IPv4 targets of course.

[atlas] check dns64/nat64 behavior ?

2020-02-21 Thread Thomas Schäfer
Hi, is there a simple way to check the reachability of IPv6 targets by probes behind NAT64? e.g. If I try to ping www.t-online.de with Adress Family IPv6 I get immediately the error " No IPv6 address found for target" instead of "measuremnet created". Same problem exists for DNS measure

Re: [atlas] Probes were incorrectly not tagged with the stability tags

2020-02-21 Thread Nick Hilliard (INEX)
Chris Amin wrote on 21/02/2020 12:43: Just for clarity, we do not yet tag probes as being stable over IPv5. best to be prepared all the same. Nick

Re: [atlas] Probes were incorrectly not tagged with the stability tags

2020-02-21 Thread Chris Amin
On 21/02/2020 13:32, Chris Amin wrote: > Over the past month there have been issues with the > "system-ipv[45]-stable-{1,30,90}d" tags Just for clarity, we do not yet tag probes as being stable over IPv5.

[atlas] Probes were incorrectly not tagged with the stability tags

2020-02-21 Thread Chris Amin
Dear colleagues, Over the past month there have been issues with the "system-ipv[45]-stable-{1,30,90}d" tags, which were not applied to many of the probes that should have had them. This was caused by accidental data format changes from a backend migration. The issue should now be fixed, so probe