- ripe-atlas - mailman.ripe.net

How can I reduce data usage on remote satellite-connected islands?
by chris＠gare.co.uk 09 Sep '20

09 Sep '20

Hello all, I've just become an ambassador for the RIPE Atlas programme. I have a question. I wish to deploy a number of probes to remote low-capacity satellite connected islands. These islands have strict and VERY expensive monthly usage quotas. Looking at some probes already installed, I see that the minimum bandwidth (is that the term used?) is approximately 3.3kbit/s This equates to around 1GB of data per month which represent a significant percentage of a consumer's monthly quota. I'll have a hard job convincing volunteers to act as hosts if they consume that much. Is there a way I can set 'bandwidth' to less than 10kbs or is there a workaround I can use to reduce this under my control? It has been suggested that I could out a timer on the host but that is nonworkable! Any help would be appreciated as I know that reachability is quite unreliable at times and the data I could provide would be most interesting. Chris

1 0

Extreme slowness today?
by Stephane Bortzmeyer 04 Sep '20

04 Sep '20

23 minutes before Atlas tells me there is no suitable probes with my criteria (country=SD, which does not surprise me). Same slowness for all measurements.

1 0

Software vs Hardware probes
by Marty Strong 03 Sep '20

03 Sep '20

Posting to the list hoping somebody has already found the answer :) Is there a way to filter by probe architecture, or perhaps software vs hardware probes? Marty

2 1

RIPE Atlas usage webinar (and software probe installation demo)
by Lia Hestina 02 Sep '20

02 Sep '20

Dear all, The RIPE NCC will host a two day RIPE Atlas webinar with two RIPE Atlas ambassadors as guest trainers, Anurag Bhatia and Swapneel Patnekar. If you are interested in learning to use RIPE Atlas for network monitoring and troubleshooting, and also learning how to install a RIPE Atlas software probe, please join us tomorrow. More information is available here: https://atlas.ripe.net/resources/training-and-materials/innog-webinar/ <https://atlas.ripe.net/resources/training-and-materials/innog-webinar/> If you would like to participate, please send an email to e-learning(a)ripe.net <mailto:e-learning@ripe.net>. Thank you, Lia Hestina

7 11

RIPE Atlas virtual events @ Rootconf
by Lia Hestina 02 Sep '20

02 Sep '20

Dear all, Rootconf organises RIPE Atlas related events starting next week. You will find the information of each event and how to register in the link below: Talk by Philip Paeps: https://hasgeek.com/rootconf/monitoring-internet-networks-using-ripe-atlas-… <https://hasgeek.com/rootconf/monitoring-internet-networks-using-ripe-atlas-…> Workshop by Swapneel Patnekar: https://hasgeek.com/rootconf/measuring-the-internet-using-ripe-atlas/ <https://hasgeek.com/rootconf/measuring-the-internet-using-ripe-atlas/> - Feel free to share this information with friends and colleagues who may be interested in joining and learning more about the RIPE Atlas. Kind regards, RIPE Atlas team _________

2 2

Disabling TLS 1.0 and 1.1 on RIPE Atlas anchors
by Robert Kisteleki 01 Sep '20

01 Sep '20

Dear RIPE Atlas users, We received reports that the availability of TLS 1.0 and 1.1 on RIPE Atlas anchors triggers some security alarms for some anchor hosts. Since the anchors don't host anything sensitive, and the measurment code is not expected to be affected by this, we will stop supporting these protocols on the anchors (*) as of *1 September*. We'll carry on with supporting TLS 1.2 (*) the RIPE Atlas website/UI will be unchanged for the time being although we expect similar changes in the near future Regards, Robert Kisteleki RIPE NCC

3 5

RIPE Atlas Remote Learning session in September 2020
by Lia Hestina 31 Aug '20

31 Aug '20

Dear all, The RIPE NCC will organise a remote learning session for RIPE Atlas. Monitor your network and troubleshoot it with RIPE Atlas. Create specific tailor-made measurements that suit your exact needs using API calls or the command line interface. After this session, you will be able to: Monitor your network using RIPE Atlas measurements Troubleshoot your network using measurements from RIPE Atlas Use the RIPE Atlas command line interface and the API to create tailor-made measurements Pre-requisites: Basic knowledge of networks How the Internet works Basic knowledge of IP, ASN, domains Familiarity with pings and traceroutes Thursday, 17 September 2020, Timezone in UTC 08:00-10:00 <https://www.timeanddate.com/worldclock/converter.html?iso=20200917T080000&p…> Registration: RIPE NCC member, register here: https://lirportal.ripe.net/training/register/courseCode/MET20200006 <https://lirportal.ripe.net/training/register/courseCode/MET20200006> For non members please send an email with your name and email address to training(a)ripe.net <mailto:training@ripe.net> If you have any question about the event, please send email to training(a)ripe.net Kind regards, RIPE Atlas team _________

1 0

WARNING - was Re: Trying to measure Quad9 latency
by Robert Kisteleki 14 Aug '20

14 Aug '20

Dear All, The email below made it to the mailing list, but it seems it so had an attachment which contains a virus. It may be useful to say it explicitly: DO NOT OPEN THE ATTACHMENT Regards, Robert On 2020-08-12 09:09, ripe-atlas wrote: > Re: [atlas] Trying to measure Quad9 latency > > ripe-atlas > ripe-atlas-bounces(a)ripe.net > > [snip]

1 0

[Moderated]
by ripe-atlas 12 Aug '20

12 Aug '20

This message was removed from the archive because it contained malware.

1 0

Re: [atlas] [RIPE-NCC/ripe-atlas-software-probe] Software probes only connect to one controller? (#45)
by Chriztoffer Hansen 10 Aug '20

10 Aug '20

On Mon, 3 Aug 2020 at 12:14, Philip Homburg <notifications(a)github.com> wrote: > This is not an ideal place to discuss how atlas works. It would be better to use the atlas mailing list (https://lists.ripe.net/mailman/listinfo/ripe-atlas). > > In any case, we have 2 controllers for software probes. Those controllers are kept separate from controllers for hardware probes. We placed both controllers at Hetzner and unfortunately, Hetzner seems to have some issues recently (or at least more than I remember). Typically a controller handles about 500 probes, so it will take some time before we will get controllers in other places in the world. > > Quite a bit of atlas backend logic depends on probes having just one controller at a time, so this is unlikely to change soon. > > Sending probes to different controllers happens automatically, but it happens on a time scale of around 6 hours. It seems that the issue at Hetzner was less than 2 hours. However, with all controllers for software probes at Hetzner, a long failure at Hetzner would indeed impact all software probes. In this case, why not have the software probes set up with a fall-back RIPE Atlas Anchor (controller)? E.g. - Setup a list of 2 or more Anchors in a hierarchical order, - If the software probe cannot reach the primary Anchor for more than 10-20 minutes., fall-back to the next Anchor reachable, - Retest connectivity to all configured anchors every 6 hours, - Revert to use the first reachable anchor in the locally configured list (a hierarchical order). * The above idea assumes an Anchor being able to temp. handle more than the default ~500 probes per Anchor, plus co-location diversity of >= 2 providers and >= 3 anchors. -- Chriztoffer

2 1

Far remote probe 34512 offline but partially works
by ripe＠brite.cz 27 Jul '20

27 Jul '20

Hi team, I have probe 34512 in distant location [not able to have it checked physically for some more time], it shows offline since 2020-07-21, no SOS messages listed since 2020-05-16. But other devices connected to the same router do work online, and also the router keeps sending me Log Messages via internet so its internet connection has to be working fine. Router log shows DHCP request getting from the Probe every 12 hours, as usually: 2020/07/27 18:51:44 Info 93-153-42-167.customers.tmcz.cz daemon dnsmasq-dhcp DHCPACK(eth1) 192.168.222.220 c0:25:e9:a8:57:96 2020/07/27 18:51:44 Info 93-153-42-167.customers.tmcz.cz daemon dnsmasq-dhcp DHCPREQUEST(eth1) 192.168.222.220 c0:25:e9:a8:57:96 The router itself is behind NAT and I'm not able to remote to it and proceed with further investigation. From the Log above I see the Probe is running and keeps requesting DHCP requests as usually, so not sure how it could show offline. Do you have any further logs or a way how to try to resurrect the Probe remotely? Thank you Jiri

1 0

Anyone with some spare credits for my experiments?
by JJ de Ronde 13 Jul '20

13 Jul '20

10 10

Issue in rendering built in graphs
by Anurag Bhatia 08 Jul '20

08 Jul '20

Hello Seems like something broken at the RIPE backend. Unable to render built-in graphs. I am getting this on any of the probes I check: URL: https://atlas.ripe.net/probes/17011/#!tab-builtins [image: Screenshot 2020-07-07 at 10.30.24 PM.png] Anyone with an idea on what's going around? -- Anurag Bhatia anuragbhatia.com

2 3

probe offline/lock up
by Bryan Fields 06 Jul '20

06 Jul '20

I had an interesting alert yesterday, as my probe 54858 said it was offline. I was unable to ping it from the router port it's directly connected to, but did some some traffic on the port via the counters. There was a fresh ARP entry as well. I power cycled it and it came back online. I was then able to ping it via v4 after it DHCP'd it's address. v6 pings were working to it's SLAAC address too. It has not gone offline now, but I am noticing pings on v4 are not working at all again. v6 seems unaffected. Is this normal or is there a problem with my probe? I've never really taken this close of a look before, I'm unsure if it has an issue or if this is normal. Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

2 2

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