- ripe-atlas - mailman.ripe.net

Is there a way to de-register a long dead probe?
by Kyriacos Sakkas 09 Feb '21

09 Feb '21

Hi All, Can't seem to find a way to just mark a long dead probe as such. Thanks, Kyriacos

3 6

atlas probe down : ID 35603
by MAYER Hans 08 Feb '21

08 Feb '21

Dear All, Our Atlas probe with ID 35603 is down since about 6 days. It’s a V3 probe. Model: TL-MR3020(UN) Ver: 1.9 ; S/N: 2176197008302. When I realised it this atlas probe was not ping-able. ( due to a power outage ) I followed the instructions https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro… with solution 1. Unfortunately it didn’t work. During the time without USB stick the probe was on the network reachable, getting the IP from DHCP. But later on, it wasn’t ping-able. So I tried solution 2. I took a different USB stick as described. After a while the probe is now ping-able. ( 2001:628:21f0:911:c225:e9ff:fea8:6530 , 147.125.100.34 , DNS name: ripencc.iiasa.ac.at<http://ripencc.iiasa.ac.at> ) But when I go to https://atlas.ripe.net/probes/35603/ I see it is offline. The web page says „no flash drive“ and „trying to connect“. What else can I do ? It seems, that the TP-Link device itself isn’t broken. Shall I try with a different USB stick. (a third one) I took a 64MB USB stick. Was this maybe too big ? I saw the original stick had only 1 MB. The documentation says it should have at least 4GB. Any ideas ? Any feedback is welcome. Kind regards Hans -- Ing. Dipl.-Ing. Hans Mayer Systems Analyst Network Unix Security Team (NUST) Information and Communication Technologies (ICT) International Institute for Applied Systems Analysis (IIASA) Schlossplatz 1 A-2361 Laxenburg, Austria Phone: +43 2236 807 Ext 215 Mobile: +43 676 83 807 215 Web: http://www.iiasa.ac.at E-Mail: hans.mayer(a)iiasa.at<mailto:hans.mayer@iiasa.at> Note: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it.

2 6

querying the config
by Randy Bush 04 Feb '21

04 Feb '21

howdy so i wanted info about a probe's config, specifically what dns resolver(s) it is using. i could not figure out how to do this. assuming it was a lack of clueons, i asked a friend with far deeper atlas fu. they said such queries are not available. really? [ yes we have bright ideas on how to discover this indirectly by mining past data ] but really? randy

5 6

Measuring reachability query
by Hank Nussbacher 27 Jan '21

27 Jan '21

2 1

atlas streaming data broken?
by Teun Vink 20 Jan '21

20 Jan '21

Hi, RIPE Atlas API streams seem to have broken down today at ~12.05h CET. Is this a known problem? Best regards, -- Teun Vink BIT | teun(a)bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE

4 8

"Ripe Atlas > Measurements, Maps and Tools > Tools" web portal not working?
by chris lee 12 Jan '21

12 Jan '21

Hi, Not sure am I missing something , as all the tools links under https://atlas.ripe.net/measurements-and-tools/tools/ don't seem to be working. It just stays on the same landing page when clicked. Thx, Chris Lee

2 1

Automating software probe creation?
by Steve Gibbard 04 Jan '21

04 Jan '21

I’m working on creating some Raspberry Pi-based software probes, to put in some networks that currently lack Atlas probes. I’d like to have a standard image that can come up and work wherever an individual probe lands, instead of needing to configure each one separately. As far as I can tell from the documentation, it looks like the probes are identified by the encryption keys in /var/atlas-probe/etc/probe-key* . If creating new probes from an image, is it sufficient to make each probe generate its own encryption keys, or are there other files that need to change? For registering the probes, I see a web form that requires being logged into a RIPE account, and don’t see any equivalent in the API documentation. Is there a way to register new software probes via the API? Thanks, Steve

7 9

Anyone else getting high requests for hitlist-rr6.hitlist.sdstrowes.co.uk
by Anurag Bhatia 28 Dec '20

28 Dec '20

Hello everyone, There seems to be high regular request on my for hitlist-rr6.hitlist.sdstrowes.co.uk. Anyone else getting the same? Since the DNS fails and it gives SERVFAIL, wondering why it's going on from over a day now. Thanks. -- Anurag Bhatia anuragbhatia.com

4 5

new website, but outdated information
by Thomas Schäfer 15 Dec '20

15 Dec '20

Hi, https://atlas.ripe.net/resources/announcements/ (Technical Updates) the last version mentioned there is: 4965 Now we are at 5020. same here: https://atlas.ripe.net/resources/source-code/ (except the link to github, that's up to date) https://atlas.ripe.net/resources/code/ Contributed Code on GitHub (https://atlas.ripe.net/github ) link is dead. Regards, Thomas

2 1

Probes suffering DNS interception?
by Ray Bellis 15 Dec '20

15 Dec '20

Is there any RIPE policy about whether nodes that are subject to DNS interception should be excluded from results (or maybe even dropped altogether) ? While these probes are perhaps still useful for ping and traceroute tests, they are effectively useless for DNS related tests other than as a proxy measure for how prevalent that practise actually is. For the visualisation I've just been building based on the Root System's "hostname.bind" data returned by Atlas it was pretty difficult to figure out how to exclude those probes on the client side. If there was a heuristic that could be applied on the probe itself or within the RIPE data collector that tagged the probe as having "bad DNS" that would help a lot. cheers, Ray Bellis Director of DNS Operations, ISC.

10 11