Probe questions - reporting clearly busticated probe configs?
Howdy! I've been running a few measurements over the last while and looked at the raw results like: [{"dst_name":"2001:4860:4860::8844","error":{"socket":"connect failed Network is unreachable"},"from":"fd84:d527:5183:0:a2f3:c1ff:fec4:63a8","fw":4940,"group_id":18903906,"lts":21,"msm_id":18903906,"msm_name":"Tdig","prb_id":13635,".... "from":"2001:db8:4447:0:eade:27ff:fec9:7134","fw":4940,"group_id":18903906,"lts":7,"msm_id":18903906,"msm_name":"Tdig","prb_id":26725,"...] I'm curious if/how atlas reports back to probe owners: "Hey, your ipv6 connectivity is implausible/impossible" since, at least for: https://atlas.ripe.net/probes/26725/#!tab-network and: https://atlas.ripe.net/probes/13635/#!tab-network there's no way their v6 addresses can work... (one is documentation prefix the other is ULA I think?) I suppose test requestors should check the ipv6 prefix to see if it's at least plausibly correct until some signal back to the owners can be attempted?
On Jan 16, 2019, at 1:18 PM, Christopher Morrow <christopher.morrow@gmail.com> wrote:
Howdy! I've been running a few measurements over the last while and looked at the raw results like:
[{"dst_name":"2001:4860:4860::8844","error":{"socket":"connect failed Network is unreachable"},"from":"fd84:d527:5183:0:a2f3:c1ff:fec4:63a8","fw":4940,"group_id":18903906,"lts":21,"msm_id":18903906,"msm_name":"Tdig","prb_id":13635,".... "from":"2001:db8:4447:0:eade:27ff:fec9:7134","fw":4940,"group_id":18903906,"lts":7,"msm_id":18903906,"msm_name":"Tdig","prb_id":26725,"...]
I'm curious if/how atlas reports back to probe owners: "Hey, your ipv6 connectivity is implausible/impossible"
since, at least for: https://atlas.ripe.net/probes/26725/#!tab-network and: https://atlas.ripe.net/probes/13635/#!tab-network
there's no way their v6 addresses can work... (one is documentation prefix the other is ULA I think?)
I suppose test requestors should check the ipv6 prefix to see if it's at least plausibly correct until some signal back to the owners can be attempted?
You should be selecting probes with the system-ipv6-works tag https://atlas.ripe.net/docs/probe-tags/ - jared
On Wed, Jan 16, 2019 at 1:55 PM Jared Mauch <jared@puck.nether.net> wrote:
On Jan 16, 2019, at 1:18 PM, Christopher Morrow < christopher.morrow@gmail.com> wrote:
Howdy! I've been running a few measurements over the last while and looked at the raw results like:
[{"dst_name":"2001:4860:4860::8844","error":{"socket":"connect failed Network is unreachable"},"from":"fd84:d527:5183:0:a2f3:c1ff:fec4:63a8","fw":4940,"group_id":18903906,"lts":21,"msm_id":18903906,"msm_name":"Tdig","prb_id":13635,"....
"from":"2001:db8:4447:0:eade:27ff:fec9:7134","fw":4940,"group_id":18903906,"lts":7,"msm_id":18903906,"msm_name":"Tdig","prb_id":26725,"...]
I'm curious if/how atlas reports back to probe owners: "Hey, your ipv6 connectivity is implausible/impossible"
since, at least for: https://atlas.ripe.net/probes/26725/#!tab-network and: https://atlas.ripe.net/probes/13635/#!tab-network
there's no way their v6 addresses can work... (one is documentation
prefix the other is ULA I think?)
I suppose test requestors should check the ipv6 prefix to see if it's at
least plausibly correct until some signal back to the owners can be attempted?
You should be selecting probes with the system-ipv6-works tag
DOH! :( ok, fine. (thanks)
https://atlas.ripe.net/docs/probe-tags/
- jared
On Wed, Jan 16, 2019 at 2:16 PM Christopher Morrow < christopher.morrow@gmail.com> wrote:
On Wed, Jan 16, 2019 at 1:55 PM Jared Mauch <jared@puck.nether.net> wrote:
On Jan 16, 2019, at 1:18 PM, Christopher Morrow < christopher.morrow@gmail.com> wrote:
Howdy! I've been running a few measurements over the last while and looked at the raw results like:
[{"dst_name":"2001:4860:4860::8844","error":{"socket":"connect failed Network is unreachable"},"from":"fd84:d527:5183:0:a2f3:c1ff:fec4:63a8","fw":4940,"group_id":18903906,"lts":21,"msm_id":18903906,"msm_name":"Tdig","prb_id":13635,"....
"from":"2001:db8:4447:0:eade:27ff:fec9:7134","fw":4940,"group_id":18903906,"lts":7,"msm_id":18903906,"msm_name":"Tdig","prb_id":26725,"...]
I'm curious if/how atlas reports back to probe owners: "Hey, your ipv6 connectivity is implausible/impossible"
since, at least for: https://atlas.ripe.net/probes/26725/#!tab-network and: https://atlas.ripe.net/probes/13635/#!tab-network
there's no way their v6 addresses can work... (one is documentation
prefix the other is ULA I think?)
I suppose test requestors should check the ipv6 prefix to see if it's
at least plausibly correct until some signal back to the owners can be attempted?
You should be selecting probes with the system-ipv6-works tag
DOH! :( ok, fine. (thanks)
hey wait.... The first of my examples: https://atlas.ripe.net/probes/26725/#!tab-general has: System Tags V3 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 at least the second one (https://atlas.ripe.net/probes/13635/#!tab-general) has: V3 Resolver Mangles Case IPv4 Works IPv6 Doesn't Work IPv4 Capable IPv6 Capable IPv6 ULA IPv4 RFC1918 IPv4 Stable 1d "system-ipv6-doesn't work"
https://atlas.ripe.net/docs/probe-tags/
- jared
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
On Fri, Jan 18, 2019 at 5:40 AM Chris Amin <camin@ripe.net> wrote:
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?
oh nat in v6 .. of course :( I thought the whole point of v6 was to not have nat, joy! ok, you're probably 100% correct. #learningalways.
On 23 Jan 2019, at 04:48, Christopher Morrow <christopher.morrow@gmail.com> wrote:
On Fri, Jan 18, 2019 at 5:40 AM Chris Amin <camin@ripe.net> wrote: 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?
oh nat in v6 .. of course :( I thought the whole point of v6 was to not have nat, joy! ok, you're probably 100% correct. #learningalways.
It may be NPTv6, rather than NATv6, but .... Tim
Hi, On Wed, Jan 23, 2019 at 09:52:19AM +0000, Tim Chown wrote:
It may be NPTv6, rather than NATv6, but ....
https://www.youtube.com/watch?v=v26BAlfWBm8 Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
On Wed, Jan 23, 2019 at 4:55 AM Gert Doering <gert@space.net> wrote:
Hi,
On Wed, Jan 23, 2019 at 09:52:19AM +0000, Tim Chown wrote:
It may be NPTv6, rather than NATv6, but ....
'yer killin me smalls' :) (I think the overall problem I have is figuring out all the 'random' filtering options, which is something shiould have spent more time figuring out :( ha! also, still love this video, thanks!
participants (5)
-
Chris Amin -
Christopher Morrow -
Gert Doering -
Jared Mauch -
Tim Chown