- ripe-atlas - mailman.ripe.net

New on RIPE Labs: Exploring RIPE Atlas Traceroutes from 2012 to 2019
by Antony Gollan 09 Aug '21

09 Aug '21

Dear colleagues, In a new article on RIPE Labs, Nevil Brownlee presents an analysis of RIPE Atlas traceroutes for days in 2012, 2015, 2017 and 2019 with full network graphs for each successive half-hour, and develops an algorithm for finding node or edge outages of an hour or more: https://labs.ripe.net/author/nevil/exploring-ripe-atlas-traceroutes-from-20… Kind regards, Antony Gollan Communications Team Leader RIPE NCC

1 0

Upgrade existing Anchor to newer hardware
by Cathal Mooney 05 Aug '21

05 Aug '21

Hi, I am working for the Wikimedia Foundation, and we have several Atlas Anchor's deployed at various locations. Some time ago the Anchor we had in our location in Dallas, US (p6093.probes.atlas.ripe.net) failed due to a hardware failure. We are now attempting to replace the Anchor with new hardware which we have installed. The old device was a v2 Anchor (Soekris), however, and the new device is v3 (PC Engines APU.2E2). Given the newer hardware I expect we will need a different USB image to boot from? Our hope would be to re-use the previous IP addressing and other details so that does not need to change. What might be the best way to approach this? Many thanks, Cathal.

2 2

Representative probe sets in eyeball networks by country
by Bart van der Sloot 21 Jul '21

21 Jul '21

Hi RIPE Atlas community, Can anyone recommend/provide predefined probe sets which provide a fair representation of the eyeball networks in a country, e.g. “10 probes in each of the Top 5 eyeball networks in France” – and preferably probes that are “in” these eyeball networks (and/or close to their interconnection routers – where they peer or connect to their Transit providers, decreasing the dependency on last mile access and in-home networks) and probes that have a high uptime? Thanks in advance for your reactions! Kind regards, Bart van der Sloot Managing Director Leaseweb Network Leaseweb Network B.V. +31 20 316 0237 +31 6 5249 8035 b.vandersloot(a)network.leaseweb.com www.leaseweb.com Hessenbergweg 95, 1101 CX Amsterdam, the Netherlands © Leaseweb Network B.V. and FiberRing, Hessenbergweg 95, 1101 CX Amsterdam, is filed with the Chamber of Commerce under registration nr. 30188570, in the Netherlands. This email including any attachments contains confidential information from us. If you have received this email message in error or unauthorized by us, please immediately notify us by replying, keep the message strictly confidential and immediately delete the email message including all attachments. Leaseweb and FiberRing are the registered trademark under which Leaseweb Network B.V. as separate and independent Leaseweb sales company provides services in a particular geographic area, subject to the FiberRing B2B Sales Terms and Conditions. Please see www.fiberring.com for more information.

1 0

anchor disk recovery
by Matthieu Herrb 20 Jul '21

20 Jul '21

Hi, after a power outage, our anchor got its grub.cfg file corrupted. I managed to use a .rpmsave boot.cfg that was present on the disk and boot into the recovery kernel. >From here the anchor is alive again on the management interface at https://atlas.ripe.net/probes/7000/ but I guess it's still in a unstable state. What is the procedure to actually repair the installation ? Should I re-install it from the USB image, or is there something else I can do remotely ? x -- Matthieu Herrb

1 0

Latest data point shown is from 2021-07-16 10:43 UTC
by Thomas Schäfer 19 Jul '21

19 Jul '21

Hi, I run two independent software probes. Looking at the graphs "Built-ins" I get the orange text: "Latest data point shown is from 2021-07-16 10:43 UTC" It only happens on the software probes. My hw probe seems to run without that problem. All three probes are online "Your probe is currently connected" Regards, Thomas

2 1

Removing virtual RIPE Atlas probe
by Milad Afshari 18 Jul '21

18 Jul '21

Hello everyone, I hope you are doing well, I am curious to know if there is any way to remove a virtual RIPE Atlas probe from my panel? Sincerely yours; Milad Afshari

2 1

Unable to create measurements in RIPE Atlas
by Salvador Bertenbreiter 12 Jul '21

12 Jul '21

Hi guys, I hope you're doing well. I am preparing an article about latency in LATAM and I would like to use RIPE Atlas to gather some data, unfortunately, I'm not being able to create my first measurement, I completed the three first steps: 1) Ping x.x.x.x 2) Selected 10 probes in Peru 3) Choose the time interval But when I click on the Create My Measurement(s) button nothing happens, I don't even receive an error message about a missing or wrong field. Any idea what could be happening? Are you able to create measurements without issues? Thank you Best regards, -- Salvador Bertenbreiter (+51) 947 145 352

1 0

Getting RRSIG records when do bit is set
by pravicha 07 Jul '21

07 Jul '21

Hello, When I set the do bit in dig, I get back RRSIG records associated with the Query Type, but I don’t get the RRSIGs when I create a measurement with do bit set in Ripe Atlas. Can I replicate the same behavior in RIPE atlas? Thanks

2 8

Is there a way to find the resolver used by the probe?
by pravicha 06 Jul '21

06 Jul '21

Hello, I’ve been trying to get dns measurements for a couple of domains over different regions using atlas probes. Is there a way to find the resolver’s IP used by the probes when use_probe_resolver is set to true? Thanks

3 3

Resolves AAAA Correctly, Doesn't Resolve A - best way to resolve this?
by Peter T Garner 28 Jun '21

28 Jun '21

I've been having a few problems setting up my software probe, but this has now almost stabilised. It's been quite an education in DNS setup! My problem now is that my probe General Information is reporting "Resolves AAAA Correctly, Doesn't Resolve A, IPv4 Stable 1d, IPv4 Works, Software IPv4 RFC1918, IPv4 Capable" but I can't seem to fix the "Doesn't Resolve A" problem: is there anything specific that I can try from the command line to diagnose this? FWIW, all other traceroutes, pings, digs etc on the box seem to be working.

1 0