- ripe-atlas - mailman.ripe.net

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