- ripe-atlas - mailman.ripe.net

Ripe atlas: Fetch all probes data
by Niraj Sorathiya 29 Jun '20

29 Jun '20

Hello Team, Is there any way to fetch all probes data at once using "ripe.atlat.coustea" python API instead downloading dump provided by Ripe team ? Thank you ! Regards, Niraj

2 3

retrieve past measurements
by Fabiano D'Agostino 29 Jun '20

29 Jun '20

Good evening, I am trying to retrieve streaming data as described in the guide here: https://atlas.ripe.net/docs/result-streaming/ I was able to retrieve the measurement results using stream_type="result", but when I try to retrieve past measurements with the startTime flag it is not working. How can I solve? Thanks in advance, Fabiano

1 0

New on RIPE Labs: Measuring IP Connectivity with RIPE Atlas
by Mirjam Kuehne 26 Jun '20

26 Jun '20

Dear colleagues, During a hackathon Branimir Petricevi and his colleagues at Leaseweb wanted to measure network performance that most accurately simulates a customer's experience with a network. They used RIPE Atlas to do that. Find out more in this new RIPE Labs article: https://labs.ripe.net/Members/branimir_petricevic/measuring-ip-connectivity… Kind regards, Mirjam Kühne RIPE NCC

3 2

Unauthorised probe transfers
by Paul Eagles 24 Jun '20

24 Jun '20

Hello, I've just had 2 emails saying that 2 of my software probes (numbers 1000305 & 1000137) have been transferred to LeaseWeb NOC. Both these probes (and another) live on LeaseWeb VPSs (one in NL, one in USA) but I haven't started or authorised a transfer. Before I go and shout at then, how could this have happened? Checking in 'My Atlas' it does indeed no longer show these as being my problems. Why would the good people at RIPE allow transfer of 2 of my probes without my approval? Yours, Paul.

4 6

Who wants 52.4M credits?
by Paul Eagles 24 Jun '20

24 Jun '20

I've got 52.4M credits that I don't need. Does anyone want them? Cheers, Paul.

3 2

dead v1 probe
by Gert Doering 22 Jun '20

22 Jun '20

Hi, have there been software updates for v1 probes recently? I've heard about a few v1 probes that have died "just last week" - mine among them (#461), fell off the net with "Firewall Problems Suspected", but it's no longer even ARPing properly (= either it totally lost its config and wants DHCP now, which there isn't in this network, or it just died)... So knowing whether this is a more widespread issue and possible reasons would help me to decide how much effort to invest in debugging this. gert -- 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

10 12

RIPE Atlas Software Probes
by Philip Homburg 22 Jun '20

22 Jun '20

Dear colleagues, We are glad to announce that, after several months of development and testing, we are now accepting applications for RIPE Atlas software probes. With several different installation options to choose from, software probes provide future hosts a whole new way to get involved with RIPE Atlas. For more details, see our new article on RIPE Labs: https://labs.ripe.net/Members/alun_davies/ripe-atlas-software-probes Kind regards, Philip

18 37

Notifications
by Thomas Schäfer 18 Jun '20

18 Jun '20

Hello, is there a possibility to get notified if the probe has lost IPv6 connectivity? At the moment it seems to me, notification only works if the connection is down with both protocols. Regards, Thomas

5 5

Q/ if Id 2303 works as expected?
by Schaefer, Henry 11 Jun '20

11 Jun '20

Hi RIPE-Atlas team, my ripe probe 2303 shows as being up and running, it is connected in a NAT environment. The probe does not show data for the Built-Ins (e.g. No data available for 2303 / 1009 for this time period) as well as is not participating in measurements. Can you check/confirm that it is not broken or advise what I would need to do to make it work like other probes please? Thanks & Regards Henry Schaefer. [image: Verizon Business Ready] <http://www.verizon.com/business> Henry Schaefer Verizon Business Markets Elisabethstraße 29-31 12247 Berlin, Germany O +49 (0)30.7669.1525 | M +49.173.262.8459 henry.schaefer(a)de.verizon.com [image: Facebook] <http://www.facebook.com/verizon> [image: Twitter] <http://twitter.com/verizon> [image: Instagram] <http://www.instagram.com/verizon> ====================================================================== Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Detlef Eppig - Vorsitzender des Aufsichtsrats: Francesco de Maio

1 0

Turris SW probe - long time to connect
by Jan Pavlinec 04 Jun '20

04 Jun '20

Hello, Since this week based on report [1], [2] from Martin we were able to observe his issue, which he reported and by using Atlas SW Probe 5010 and older, we noticed that in CLI probe is running and that it is doing something, but on the RIPE website, it shows that probe is disconnected. Can you please check probes IDs (1000585, 1000243) and what it took so long to show that it is connected? Both of those probes were shown as connected at the same time - 20:22) on Tuesday? We noticed that in some cases if you were using the latest version 5020 and register a new probe, it is working within a few minutes. However, we pushed to all our Turris OS version updated Atlas SW Probe to version 5020 and some of our users noticed similar maybe the same behavior. A probe was running on the router, but it was disconnected for almost an hour (probe ID 1000036) The router is working in all cases, ping, dig connection is OK. I'm wondering if this issue isn't on server side. In reg_init_reply.txt were following data: WAIT TIMEOUT 115 Do you know how to debug it more? [1] https://forum.turris.cz/t/turris-os-5-0-0-is-released-in-hbt/12733/149 [2] https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/38 Looking forward to hearing from you, Jan

1 0

Feature request DNS DoH measurement
by Yang Yu 25 May '20

25 May '20

Hi, As DoH is getting more adoption, it would be interesting to have DoH query support on Atlas. With support added as an additional protocol for DNS measurement (currently TCP/UDP), most measurement creation/result parsing settings can be reused. Yang

3 3

anchor on a /32 network with on-link routing ?
by Matthieu Herrb 24 May '20

24 May '20

Hi, here at Tetaneutral.net we purchased an anchor with the idea to host it in our network. For IPv4 We are using /32 addresses everywhere, and do the routing by setting the 'on-link' flag on the default route. This configuration doesn't seem to be possible through the management interface. It complains that the gateway is not no the same network as the host and provides no way (as far as I can tell) to setup the 'on-link' flag. Apart from inserting another router in front of our anchor to let it use a narrower prefix, is there a way to set it up ? Or can this be considered for the future evolutions of the anchor software ? Thanks in advance. -- Matthieu Herrb

1 0

Looking for RIPE Atlas credits
by Nils Rodday 21 May '20

21 May '20

Dear RIPE Atlas users, As I have been using around 300M credits over the past few months and am close to running out, I would like to ask if somebody has some spare credits to transfer into my account: nils.rodday(a)unibw.de I am a PhD-student at the Bundeswehr University Munich & University of Twente. If you have credits to share, I would appreciate it. Thanks. :) Kind regards, Nils

15 23

running a probe via LTE access
by Thomas Schäfer 21 May '20

21 May '20

Hi, Has anybody experience with running a probe via LTE? I see only a little amount if I use the tags 4g or LTE, together with IPv6 as requirement, just less than 10. What is the monthly data volume you have? Is it a big problem if I run in a speed limit of 32kbit/s? Regards, Thomas

5 5

One of my hosted probes don't accept measurements
by Evgeniy S. 07 May '20

07 May '20

Dear RIPE guys, one of probes hosted by us https://atlas.ripe.net/probes/35439/ shows as connected and good to go, but when I create any measurements with this ID I see "1 Requested / None yet Actually Participating" Please advice what's wrong with it and how to troubleshoot? -- With regards, Eugene Sudyr

2 4

status-check redirects to itself?
by Stephane Bortzmeyer 30 Apr '20

30 Apr '20

Since today, status-check seems to redirect to itself? % curl -v https://atlas.ripe.net/api/v2/measurements/2060427/status-check\?permitted_… ... < HTTP/1.1 301 Moved Permanently < Server: nginx/1.16.1 < Date: Wed, 29 Apr 2020 17:57:17 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 0 < Connection: keep-alive < Location: /api/v2/measurements/2060427/status-check/?permitted_total_alerts=3 What's up?

5 5

Setting the DNS AD bit
by Stephane Bortzmeyer 15 Apr '20

15 Apr '20

It seems there is currently no way to set the AD bit in DNS queries? (Through the API, we can only control RD, CD and DO bits.)

2 1

Online hackathon: Internet Health Measurements & COVID-19
by Vesna Manojlovic 08 Apr '20

08 Apr '20

Dear all, just like many other organisations, RIPE NCC is having a COVID-19 focused hackathon with very broad goal: measuring Internet health, while focusing on RIPE Atlas, RIS & OONI data. In the third week of our online event, we have a very open, very lose collective: no registration, no prizes, no deadlines... Our results are currently mostly data-visualizations & analysis: https://labs.ripe.net/covid19 To join: * read about active projects on EtherPad, and contribute: https://pad.riseup.net/p/ripe-ncc-corona-hackathon-keep * join Jitsi for video conferencing: https://jitsi.hamburg.freifunk.net/WiseGeeseUniteCarefully * chat here: slack.ooni.org / #oon-dev (also bridged to IRC) Incremental reports are added to this article: https://labs.ripe.net/Members/becha/hackathons-in-the-time-of-corona Our next call will be on Tuesday 14. April at 11:30 AM CEST (on Jitsi) If you'd like to join one of the many other hackathons, look here: https://wiki.techinc.nl/User:Becha/COVID-19#Hackathons Stay safe, stay @ home, stay healthy... Kind regards, Vesna

1 0

No Atlas today: bad gateway
by Stephane Bortzmeyer 31 Mar '20

31 Mar '20

https://atlas.ripe.net/ 502 Bad Gateway nginx/1.16.1 COVID-19 on the server?

5 6

Re: [atlas] Probe 2285 is disconnected (Randy/Bainbridge Comcast)
by Randy Bush 21 Mar '20

21 Mar '20

i keep getting these > Your probe 2285 has been disconnected from the RIPE Atlas > infrastructure since 2020-03-18 06:43:44 UTC. status shows it down but i can ping6 the probe, and from the local gateway, i can ping4 it's natted address psg.com:/usr/home/randy> ping6 2601:600:c680:2fe:220:4aff:fee0:246d PING6(56=40+8+8 bytes) 2001:418:1::62 --> 2601:600:c680:2fe:220:4aff:fee0:246d 16 bytes from 2601:600:c680:2fe:220:4aff:fee0:246d, icmp_seq=0 hlim=56 time=13.533 ms 16 bytes from 2601:600:c680:2fe:220:4aff:fee0:246d, icmp_seq=1 hlim=56 time=12.370 ms root@wrt-biwa:~# ping 192.168.0.27 PING 192.168.0.27 (192.168.0.27): 56 data bytes 64 bytes from 192.168.0.27: seq=0 ttl=64 time=0.921 ms 64 bytes from 192.168.0.27: seq=1 ttl=64 time=0.701 ms network tab shows a long history of very short disconnects there is a strat 1 sitting on the same lan, and a lot of chimers out in the world think the strat 1 is preferred. no, that is not a definitive test in any way, but it's all i can think of at my current caffeine level. comcast? modem? v1 probe? how to better diagnose? randy

2 2

Cross-connecting Communities : hackathon about the Internet health
by Vesna Manojlovic 20 Mar '20

20 Mar '20

Dear colleagues, please join our virtual hackathon: https://labs.ripe.net/Members/becha/hackathons-in-the-time-of-corona Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Probe 2177 disconnected since Tuesday
by Werner Wiethege 20 Mar '20

20 Mar '20

The green light is on and the orange light flashes but I don't see any network traffic from it. The port LED on the switch lights up when the cable is plugged in. I have disconnected it and plugged it in again after a few hours but that didn't change anything. Werner

4 7

Software probe using port 8080
by Paul Eagles 13 Mar '20

13 Mar '20

Hi, Is there any way to change the ports that the software probes use? Port 8080 is used by the probe which conflicts with another piece of software I wanted to use. Looking in the processes I saw this: atlas 843 0.0 0.2 50348 5992 ? S 10:15 0:00 /usr/bin/ssh -o ServerAliveInterval 60 -o StrictHostKeyChecking yes -o UserKnownHostsFile /var/atlas-probe/.ssh/known_hosts -R 50948:127.0.0.1:2023 -L 8080:127.0.0.1:8080 -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)ctr-fsn01.atlas.ripe.net KEEP I had to kill the PID in order to run the other software I need so at present this new software probe is down. I'd like to start it up again but can't unless I can control which port the SSH tunnel is using. Thanks, Pauil.

3 3

Software probes offline since updating to 5010-3
by Paul Eagles 12 Mar '20

12 Mar '20

Hi all, About an hour ago I updated my 4 software probes (1000136, 1000137, 1000149 & 1000177) to 5010-3 from 5010-1 and they're all still showing as offline. For each probe I went through and updated the keys within a minute or so of the installation finishing so I don't think that's the problem. It shouldn't be an internet connection issue, they're all using the same connection as they were prior to the update and prior to the update all 4 probes were connected OK. Plus I have a physical probe at home in the same location as one of the software probes and that physical probe is showing as online. One of the software probes has been rebooted but that didn't seem to make any difference. Checking the running processes on the host everything appears OK, I see 2 instances of the ATLAS binary running. Am I missing something or just being impatient? Cheers, Paul.

2 2

(not) disconnected probes
by Romain Fontugne 11 Mar '20

11 Mar '20

Hi, I found that the following probes are reported disconnected for several hours a day, more or less at the same time, but all their built-in measurements are there and seem normal: https://atlas.ripe.net/probes/32639/#!tab-network https://atlas.ripe.net/probes/28818/#!tab-network https://atlas.ripe.net/probes/19107/#!tab-network https://atlas.ripe.net/probes/14831/#!tab-network https://atlas.ripe.net/probes/11982/#!tab-network These probes are in different ISPs and locations in Japan. Any idea why this is happening? something funky on the controllers side? Thanks, Romain

2 4