February 2019 - ripe-atlas - mailman.ripe.net

Meta-information dumps for built-in measurements?
by Vasileios Giotsas 09 Nov '20

09 Nov '20

Is there any repository like https://ftp.ripe.net/ripe/atlas/measurements/ that contains meta-information about built-in RIPE Atlas measurements (the above repository contains meta-information only for public measurements)? I couldn't find anything similar in the new FTP repository at https://data-store.ripe.net/datasets/atlas-daily-dumps/ I guess using the API is an alternative but it would be more convenient to have such dumps Thanks, Vasileios

15 24

New RIPE Atlas Version 4 Probes
by Mirjam Kuehne 26 Feb '19

26 Feb '19

Dear colleagues, In part as a response to recent questions regarding the distribution of RIPE Atlas probes, we have prepared an article detailing the work we have been doing to get supply back on track: https://labs.ripe.net/Members/alun_davies/new-ripe-atlas-version-4-probes We hope that this article, in which we introduce the new generation of RIPE Atlas probes, will answer at least some of the questions that have arisen lately. We’d like to thank you all once again for your patience! Kind regards, Mirjam Kühne RIPE NCC

1 0

Time difference between results and update of measurement status
by Vasileios Giotsas 25 Feb '19

25 Feb '19

I've seen that the status of a measurement is updated much later than when the measurement results become available. For instance, while the RTTs of a ping measurement are returned the status is still Ongoing for up to 3 minutes. Is there anything (such as sanity checks) that intervenes between the update of the results and and update of the measurement status, which may change the results? Or is it safe to assume that once the results are out the measurement status will eventually change to 'Stopped', just a bit later? Thanks! Vasileios

2 1

Issue with RIPE Atlas HTTP measurements
by Philip Homburg 19 Feb '19

19 Feb '19

We recently discovered an issue with RIPE Atlas HTTP measurements. In trying to fix an issue that caused the HTTP body size to be reported incorrectly, we inadvertently introduced a bug that prevents the measurement from working under certain conditions. This bug affects firmware release 4940 and the upcoming releases 4950 and 4960. The combination that fails is a recurring measurement after the first run with an HTTP server that returns the body as chunks. This means that one-off measurements are fine. Unfortunately, HTTP measurements that are part of anchoring measurements are affected. We will work to fix this issue in the first firmware release after 4960, which can be expected in the next couple of months. We apologise for the ongoing issue and will keep you informed as we work to resolve it. Philip

1 0

Re: [atlas] "Cannot resolve" tag on IPv6-only network?
by ripe＠brite.cz 14 Feb '19

14 Feb '19

https://atlas.ripe.net/about/faq/#i-have-an-ipv6-only-network-will-the-prob… says I have an IPv6-only network. Will the probe work on it? Yes. All probes can be configured statically with an IPv6 address, default router, DNS resolvers, etc. through the web UI. In addition, version 3 probes can be fully configured through router advertisements (support for RFC 6106 was added in firmware release 4680). There is at the moment no support for DHCPv6 (RFC 3315). Version 1 and 2 probes can obtain addresses and default routers through router advertisements, but cannot obtain DNS resolvers that way. For those probes, the DNS resolvers will have to be configured statically through the web UI. ______________________________________________________________ > Od: "Lorenzo Colitti" <lorenzo(a)google.com> > Komu: "Anand Buddhdev" <anandb(a)ripe.net> > Datum: 14.02.2019 12:47 > Předmět: Re: [atlas] "Cannot resolve" tag on IPv6-only network? > > CC: <ripe-atlas(a)ripe.net> >On Sat, Feb 9, 2019 at 7:47 PM Lorenzo Colitti <lorenzo(a)google.com> wrote: > >> IPv6-only networks are certainly supported, but if the probe isn't aware >>> of any DNS resolver, then it's not going to be able to do any of its own >>> DNS lookups, and that's why it's been tagged with the "cannot resolve" >>> tags. >>> >> >> Hmm. The network announces IPv6 DNS servers via RDNSS, and as far as I >> know, they work. Does the probe support RDNSS? >> > >I turned on IPv4 on that subnet and things started working again. That >makes me think that the probe doesn't support RDNSS. Can anyone confirm or >deny? Should I file a bug? > >

2 1

"Cannot resolve" tag on IPv6-only network?
by Lorenzo Colitti 14 Feb '19

14 Feb '19

My probe v1 is on an IPv6-only network with NAT64 and DNS64. In the web UI I see it's tagged with "cannot resolve A" and "cannot resolve AAAA". Are IPv6-only networks supported? Is this because the network doesn't have a DHCP server? Something else?

2 3

shared fate for my two probes
by Jay Borkenhagen 08 Feb '19

08 Feb '19

Hi, My two RIPE Atlas probes have been acting strangely over the past several months. Very frequently I receive automatic notices from the RIPE Atlas system that both of my probes have been "disconnected from the RIPE Atlas infrastructure" essentially simultaneously. Here's the history from 2018: probe 11171 2018-02-23 18:08:57 UTC. probe 11203 2018-02-23 18:10:23 UTC. probe 11171 2018-06-21 04:32:15 UTC. probe 11203 2018-06-21 04:30:59 UTC. probe 11171 2018-06-24 05:36:57 UTC. probe 11203 2018-06-24 05:37:04 UTC. probe 11171 2018-07-31 20:25:27 UTC. probe 11203 2018-07-31 20:25:32 UTC. probe 11171 2018-08-18 04:48:20 UTC. probe 11171 2018-09-15 02:31:26 UTC. probe 11203 2018-09-15 02:31:28 UTC. probe 11171 2018-10-15 23:03:50 UTC. probe 11203 2018-10-15 23:04:06 UTC. probe 11171 2018-11-16 14:42:28 UTC. probe 11203 2018-11-16 14:42:33 UTC. (Those last three events are eerily periodic.) Each time when I am finally able to visit inspect the probes (both are reported as "Firmware Version 4940 (1100)"), their LEDs are in the same state: --------------- Looking at the units with the on/off LED to the left: (1) the left-most (on/off) LEDs are on steadily. (2) the next LED is off. the next two LEDs are flashing at different frequencies: (3) the next flashes on approx. 48 times per minute (4) the next flashes on approx. 110 times per minute (5) the centers of the wide "WPS/RESET" LEDs are on steadily. --------------- Once these probes fail they remain offline until I try turning it off and on again. The probes are powered similarly: the RIPE-provided USB cable is plugged into an Apple iPhone USB power adapter, in turn plugged into a standard US 120v / 60 Hz AC receptacle. However, the AC power circuits feeding these receptacles come from two very different sources which should not share fate. Until today both probes have been plugged into ports on the same Cisco switch, but after today's disconnect I moved probe 11203 to a different physical switch that has the same VLANs. None of my other equipment experiences any troubles around the times when these events happen to my RIPE Atlas probes. In the past I have reported these events to atlas(a)ripe.net, but I doubt that the causes cited (e.g. "the problem is with your dns") have been accurate. (I do not blame the atlas(a)ripe.net folks who have responded. Something strange is happening here, and I haven't yet cracked it.) I'm curious whether anyone else sees similar behaviors, or has suggestions for ways to determine what is happening. Thanks! Jay B.

3 5

New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution
by Mirjam Kuehne 08 Feb '19

08 Feb '19

Dear colleagues, The good news: RIPE Atlas is growing both in terms of geographical diversity and ASN coverage. What's more, RIPE Atlas is evolving, with a new generation of probe hardware having already passed the test phase and a pilot programme underway to assess the viability of VM anchors. The not so good news: With RIPE Atlas so much in demand, and with our current provider having ceased manufacturing the probe hardware, we've had to dramatically reduce the number of probes we're distributing. Please find more details on RIPE Labs: https://labs.ripe.net/Members/alun_davies/ripe-atlas-probes-delays-in-distr… Kind regards, Mirjam Kühne RIPE NCC

5 5

Re: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution
by Gert Doering 08 Feb '19

08 Feb '19

Hi, On Fri, Feb 08, 2019 at 03:32:38PM +0100, Philip Homburg wrote: > On 2019/02/08 13:45 , Micha Bailey wrote: > > Interesting. This seems like a much higher power device. What are the > > actual power requirements? So far my probe has been powered from the USB > > port on the router, and I???m concerned that this may make the > > installation of future probes more difficult. > > The power requirements are quite reasonable when used as an Atlas probe. > There should be no problem powering a v4 probe from a USB port. My v4 probe is fed from an USB port on an older Mac Mini, with no adverse effects I can see. 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

1 0