- ripe-atlas - mailman.ripe.net

RIPE NCC Open House: Feedback on our Unified User Interface
by Michela Galante 28 Mar '22

28 Mar '22

Dear colleagues, On Wednesday 6 April from 10:00 to 11:30 UTC, we invite users of RIPE Atlas, RIPE Database, RIPE Labs, RIPE NCC Academy, LIR Portal, RPKI and RIPEstat to give us feedback on our unified user interface. This Open House session will focus on the user interface that was launched in 2020. Our goal is to unify the user experience across all platforms to make it easier and faster for users to navigate our services. You can register for the event at: https://meeting-registration.ripe.net/meeting-pub/registration?0&meetingId=… More information is available on our website: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-fe… Best regards, Michela Galante RIPE NCC

1 0

problem reusing probes
by Cristel Pelsser 28 Mar '22

28 Mar '22

Hi, I have a problem reusing probes from previous measurements. I’m launching experiments in pairs from the web interface. I would like to retrieve the probes selected randomly in one experiment for another measurement that takes place at the same time. My problem is that it takes time to show the measurement I created in the list of "my measurements". Even when all measurements are shown in the list of all "my measurements", the creation interface does not find all these measurement ids. So I cannot retrieve the probes I need. Is there an access problem to the measurement DB or am I doing something wrong? Cristel

1 0

Problem with DoT measurements?
by Stephane Bortzmeyer 24 Mar '22

24 Mar '22

DoT measurements seem partially broken, only 10 % of the probes do report. (See for instance #39675721.)

2 1

Facebook in Russia and a diagnostic problem
by Stephane Bortzmeyer 14 Mar '22

14 Mar '22

Around half of the RIPE Atlas probes in Russia cannot complete a TLS session with facebook.com <https://atlas.ripe.net/measurements/39387725/>. (All the remaining tests have been done with the same set of probes, 'type': 'msm', 'value': '39387725'.) They have no problem with YouTube <https://atlas.ripe.net/measurements/39387839>. I also did TLS tests with IP addresses instead of names, same result <https://atlas.ripe.net/measurements/39387985> <https://atlas.ripe.net/measurements/39388031>. There is no lying DNS resolver <https://atlas.ripe.net/measurements/39387902>. But traceroute show no connectivity problem either, we can go to the Facebook AS from Russia <https://atlas.ripe.net/measurements/39388122> <https://atlas.ripe.net/measurements/39388176>. So, I'm a bit lost: what do we observe? It does not look like censorship but not like a connectivy issue (because of depeering by Cogent and Lumen) either.

6 7

Re: [atlas] Facebook in Russia and a diagnostic problem
by Stephane Bortzmeyer 14 Mar '22

14 Mar '22

On Mon, Mar 14, 2022 at 01:40:02PM +0100, Emile Aben <eaben(a)ripe.net> wrote a message of 21 lines which said: > I find the things the OONI project does very insightful. > > For this particular case: > https://ooni.org/post/2022-russia-blocks-amid-ru-ua-conflict/ Good reference, thanks, it explains everything.

2 1

broken atlas streams
by Teun Vink 04 Mar '22

04 Mar '22

Hi, We’re seeing some issues with RIPE Atlas streams using the ripe.atlas.cousteau websocket library. Sockets seem to connect properly, but no data is received. tcpdumps show very little traffic. One of the already running receiver application (monitoring the exact same set of measurements) is receiving data, but any newly started daemon fails to receive data. Is there an issue on the RIPE Atlas infrastructure? Thanks, -- Teun Vink BIT | teun(a)bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE

2 4

How to run the RIPE Atlas software probe on FreeBSD
by Eric Kochen 03 Mar '22

03 Mar '22

Hi, Anyone ever managed to get the RIPE Atlas software probe running on FreeBSD? I am thinking of installing it on my pfSense system. Cheers, Eric

6 5

My Atlas > Credits reporting wrong total daily income?
by Jaewon Kim 19 Feb '22

19 Feb '22

Hello, List! First of all, this is my first time posting to any kind of mailing list, so apologies if I did something wrong. Please let me know if so. I'm having this weird issue where 'My Atlas' page showing wrong info for "total daily income" (around 2x of what I'm actually getting). As you can see above, Atlas is reporting that this specific probe is earning 64K a day, and the total income is around 615K. However, if I see the actual credits page, None of my probes are actually earning that much. Plus, the hourly income is 13.7K, which sums up to around 330K/day. This isn't a big issue to be honest, but just got curious (and confused) with it. If anyone knows a fix for it, or why this is happening, it would be great :) Thank you! Best regards, Jaewon.

1 0

monthly information about probe availability
by MAYER Hans 14 Feb '22

14 Feb '22

Dear All, We get this monthly e-mail about probe availability. This is great. But there are some questions. What exactly is getting measured? Is this a connection to some external site? Which could mean that there are other factors that could influence the measure (i.e. that external site is down, etc.) Kind regards Hans —

3 4

Ripe Atlas Credits Request
by Андрей Дорофеев 07 Feb '22

07 Feb '22

Hi, again Sergio. If you wanna more probes for research, I can gave you API key or access to my probe.

1 0

Ripe Atlas Credits Request
by Sergio Ricardo Hernandez Torres 07 Feb '22

07 Feb '22

Hello Ripe Atlas Community: My name is Sergio R. Hernández Torres, and I’m currently a Master’s student at KTH Royal Institute of Technology in Stockholm, SE. A little more than a year ago, in November 2020, I was deeply inspired by RIPE's mission and RPKI route validation, thanks to a guest lecture from RIPE at KTH. At this moment, I am currently beginning to work on my Master’s Thesis and chose to do it related to RPKI Validation. To run some experiments, I’m reaching out to you to know if it is possible to obtain RIPE Atlas credits for Academic Purposes. Also, I would like to keep in touch if more RPKI or routing information is needed! My Ripe Atlas account where donations are accepted is: srht(a)kth.se<mailto:srht@kth.se> Best Regards, Sergio R. Hernández Torres Student | Master's Programme, Communication Systems KTH Royal Institute of Technology www.kth.se<http://www.kth.se/>

11 11

Re: [atlas] Ripe Atlas Credits Request
by Андрей Дорофеев 07 Feb '22

07 Feb '22

Send you near 6.9m Enjoy. Best regards, Andrey.

1 0

Update Wikipedia Article?
by Paul Theodoropoulos 03 Feb '22

03 Feb '22

I was curious what Wikipedia has to say about the project so had a look. The article is...adequate, but could use some updating and expansion. Unfortunately, I am merely a helpful little Probe, without as much insight into the true dynamics of the Atlas unlike many others here. For one thing, there's no mention of the ability to run software probes as I do. I made a few "WikiGnome" fixes on the article, but other than that, I'm not really the person to update it... Just tossing that out there! -- Paul Theodoropoulos www.anastrophe.com

2 1

Location of probe controllers
by Malte Appel 01 Feb '22

01 Feb '22

Hi, I was looking at the built-in traceroute measurements and noticed additional targets (ctr-*.atlas.ripe.net) apart from the DNS root servers. As I understand it, these are the controllers for the probes. However, I was wondering where they are physically located and could not find any clear information about that. My guesses from the DNS names are based on IATA airport codes: ctr-ams02.atlas.ripe.net (Amsterdam, NL) ctr-ams03.atlas.ripe.net (Amsterdam, NL) ctr-ewr01.atlas.ripe.net (Newark, NJ, US) ctr-fnc01.atlas.ripe.net (Funchal, PT) ctr-nue13.atlas.ripe.net (Nürnberg, DE) ctr-nue17.atlas.ripe.net (Nürnberg, DE) ctr-sin02.atlas.ripe.net (Singapore, SG) Can anyone confirm or correct these locations? Best, Malte

6 7

Is there a procedure to move a software probe to a new device
by Peter Garner (iPad) 01 Feb '22

01 Feb '22

Noob question. I set up my software probe on a Debian 10 box which has quite a few small servers on it. However, I intend to move it onto a Raspberry Pi, so I was wondering if there's a specific procedure to follow to preserve existing settings? Only the internal IP address will change; the external remains the same.

6 7

Can't access the serial in SOA records from the API
by Nathan Larsen 26 Jan '22

26 Jan '22

Hi, Does anyone know a way to access the serials from SOA records with the Ripe Atlas API? I have been running a variety of DNS measurements with the query type being SOA, but have not been able to determine how to get serial numbers over the course of the measurement. Any guidance would be appreciated, Nate Larsen

1 0

daily income zero ripe probe 32256 credits com338.934.911
by kiran.gunana＠colruytgroup.com 21 Jan '22

21 Jan '22

Dears, Any reason why my daily income in credits is zero even though my probe is almost online everyday ? My probe ID : 32256 Also I would appreciate few donations ( 4 million credits) on credits as I need to initiate new measurements ? Kind Regards, Kiran Gunana Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website

4 3

probe V2 status lights
by Jaap Akkerhuis 18 Jan '22

18 Jan '22

There used to be information telleing what the lights mean. It seems to be gone. After a lot of searching around one finds some information about blinking orage lights but all leds in version 2 are green colored so I guess this cvers V3 (or V1?) probes. have probes V2 been abandoned by Ripe-Ncc? jaap

4 4

Re: [atlas] Possible paging bug on RIPE Atlas Probes page with iltered results
by T 14 Jan '22

14 Jan '22

Hello, It's not you, it's not your browser. It is indeed a bug that exists since the new design of the RIPE Atlas website (Quite a few months ago), I reported it in the survey of usability and improvement of the site, but apparently it still exists to this day. You can use these urls as a workaround: Pages: public=1, public=2, public=3, etc. Status=0: Never Connected Status=1: Connected Status=2: Disconnected country=US: Country code https://atlas.ripe.net/frames/probes/?public=1&search=&status=0&af=&country… https://atlas.ripe.net/frames/probes/?public=1&search=&status=1&af=&country… https://atlas.ripe.net/frames/probes/?public=1&search=&status=2&af=&country… At least it's a little more usable this way. Apparently the menus of the old design are still standing in the new design, so it does not recognize the filters. Regards, Spiroku On Sun, Jan 9, 2022 at 8:00 AM <ripe-atlas-request(a)ripe.net> wrote: > Send ripe-atlas mailing list submissions to > ripe-atlas(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ripe.net/mailman/listinfo/ripe-atlas > or, via email, send a message with subject or body 'help' to > ripe-atlas-request(a)ripe.net > > You can reach the person managing the list at > ripe-atlas-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of ripe-atlas digest..." > > > Today's Topics: > > 1. Possible paging bug on RIPE Atlas Probes page with iltered > results (Kristijonas Lukas Bukauskas) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 08 Jan 2022 21:31:16 +0200 > From: Kristijonas Lukas Bukauskas <kb(a)tsig.nl> > To: ripe-atlas(a)ripe.net > Subject: [atlas] Possible paging bug on RIPE Atlas Probes page with > iltered results > Message-ID: <3b2f50c2f2d09b3bed26285510e5c80d(a)tsig.nl> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Hello, > > I hope bugs can be reported to this mailing since it is followed and > answered by RIPE Atlas developers. > > On Probes page (https://atlas.ripe.net/probes/) when filtering results > (by any criterion), navigating to the next page (with >) results in > resetting the filter. > > Expected behavior: filtered results not only on the first, but any other > following page when navigating through pages. > > Tested with Firefox 78.15.0esr (64-bit) and Google Chrome 95.0.4638.69 > (Official Build) (64-bit). > > Is it just me or a bug? > > -- > Regards > Kristijonas Lukas Bukauskas > > > > End of ripe-atlas Digest, Vol 125, Issue 2 > ****************************************** >

3 2

Incorrect location of a probe
by Hugo Salgado 11 Jan '22

11 Jan '22

Hi RIPE Atlas. Have a happy new year! I'd like to know how you can report a probe that has a bad geolocation. It's #29811 that appears in southern Chile, but its AS and traceroutes appear to be in Canada. Unfortunately it affects all measurements that try to group geographically by country :( If the host does not cooperate, could a system tag be added indicating "suspicious location"? Thanks a lot! Hugo

3 2

Possible paging bug on RIPE Atlas Probes page with iltered results
by Kristijonas Lukas Bukauskas 08 Jan '22

08 Jan '22

Hello, I hope bugs can be reported to this mailing since it is followed and answered by RIPE Atlas developers. On Probes page (https://atlas.ripe.net/probes/) when filtering results (by any criterion), navigating to the next page (with >) results in resetting the filter. Expected behavior: filtered results not only on the first, but any other following page when navigating through pages. Tested with Firefox 78.15.0esr (64-bit) and Google Chrome 95.0.4638.69 (Official Build) (64-bit). Is it just me or a bug? -- Regards Kristijonas Lukas Bukauskas

1 0

Notification for probes going down for extended period??
by Geert Jan de Groot 04 Jan '22

04 Jan '22

Hi, I have been hosting probes for many years and, judging by the traffic seen, they have seen a fair amount of use, which is good. Despite being on a "home network", I was able to get a small subnet so the probes could run without NAT state nastyness and all. Unfortunately, the ISP providing home connectivity is changing. They used to be innovative, offering IPv6, subnet and lots of features. However the mother telco decided that innovation was bad and is changing the service offering, killing innovative services one by one. Today I received notification that the subnet the probes live on, will be de-activated on Jan 11. I've cancelled my subscription with said ISP on Jan 13 and the house will be on a different ISP then, unfortunately the new ISP is planning to provide subnet service but is in the process of setting things up and cannot provide subnet service today. What is the protocol for signalling "this probe is down and that may be for quite a bit"? And what is the protocol for signalling "this probe is now on a different topology, is no longer on AS3265 and network performance is different"? (I guess several others will have this question, answers on list please) Geert Jan

3 2

v1 Prove #266 gone offline
by Andreas S. Kerber 04 Jan '22

04 Jan '22

Hi, our v1 probe #266 has gone into a boot loop, loosing/reconnecting network link every few seconds. Is there troubleshooting advice for a v1 probe doing that? Already tried on a number other USB feeds and different switches. Andreas

2 1

NanoPi NEO Plus2 won't connect
by Marty Strong 28 Dec '21

28 Dec '21

Hi all! I moved house at the end of June and only recently got round to plugging my NanoPi NEO Plus2 probe #50010 in. It doesn't seem to connect, not even getting a DHCP lease. Is there any way to debug what's wrong with it? https://atlas.ripe.net/probes/50010/ Thanks, Marty

2 1

Announcement regarding the recently discovered log4j vulnerabilities
by Johan ter Beest 22 Dec '21

22 Dec '21

Dear RIPE Atlas probe and anchor hosts, We would like to share some information in light of the log4j issues that were recently made public. After an extensive investigation of our systems, we have determined that both the RIPE Atlas probes and the RIPE Atlas anchors are not vulnerable to the recently discovered log4j vulnerability. More information can be found in the official announcement: https://www.ripe.net/publications/news/announcements/log4j-zero-day-vulnera… We wish you happy holidays and happy measuring :) Kind regards, Johan ter Beest RIPE Atlas Team

1 0