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/[email protected]/

[ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)

Previous message (by thread): [ipv6-wg] ipv6-wg Digest, Vol 50, Issue 3
Next message (by thread): [ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jen Linkova furry13 at gmail.com
Tue Nov 3 15:23:29 CET 2015

On Tue, Nov 3, 2015 at 3:18 PM, Gert Doering <gert at space.net> wrote:

>> RIPE Atlas probe is a host. It should not care much if it's traffic is
>> going via NAT64 box or not.
>
> Actually detecting NAT64 and flagging as such, and being able to run
> tests on a group of NAT64-hidden probes might add value...

I think there is a dirty hack to do it now: run a measurements from
v6-enabled probes to v4-only host, check the results for the
destination address they were using.

But I agree, it would be nice to get a list of probes behind NAT64 w/o
wasting time and credits ;)

-- 
SY, Jen Linkova aka Furry

Previous message (by thread): [ipv6-wg] ipv6-wg Digest, Vol 50, Issue 3
Next message (by thread): [ipv6-wg] RIPE Atlas and NAT64 (Was: IPv6-only network during RIPE 71)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]