- ripe-atlas - mailman.ripe.net

DoH / DoT test in Atlas Probes
by Imre Tuskes 02 Nov '20

02 Nov '20

Hello, Is there any plan to measure DNS over HTTPs (or TLS). We are interested in the performance of this kind of service. Regards, Imre

2 1

Re: [atlas] measurements not starting
by Viktor Naumov 29 Oct '20

29 Oct '20

Sorry, my bad. I didn't rub my eyes enough. Indeed the reason is different. What I can see from the logs is that the scheduler couldn't find any probe in AS4771 that would be capable of doing v6 measurement. wbr /vty On 10/29/20 8:35 AM, Povl Ole Haarlev Olsen wrote: > On Thu, 29 Oct 2020, Viktor Naumov wrote: >> The times shown on the page are in UTC. So your measurement should >> start in about 1h 15 minutes from the current moment. > > 2020-10-28 was yesterday. > >> On 10/29/20 7:12 AM, Yang Yu wrote: >>> SCHEDULED from >>> 2020-10-28T08:41:35Z >>> to >>> 2020-11-11T00:35:07Z >>> every 900s >

2 3

measurements not starting
by Yang Yu 29 Oct '20

29 Oct '20

Hi, I created 2 measurements with start time now, but neither started after 1 day https://atlas.ripe.net/measurements/27881135/ https://atlas.ripe.net/measurements/27881134/ > SCHEDULED from 2020-10-28T08:41:35Z to 2020-11-11T00:35:07Z every 900s >none of requested probes got scheduled SCHEDULED None yet Number of probes actually scheduled for this measurement What am I missing here? Thanks. Yang

3 2

RIPE Atlas Deployathon - 25 November 2020
by Lia Hestina 27 Oct '20

27 Oct '20

Dear colleagues, As part of the 10th anniversary of RIPE Atlas, we're organising a virtual RIPE Atlas software probe deployathon. Join us on 25 November 2020 to help us celebrate 10 years of RIPE Atlas by adding 10x10 software probes over 10 hours! You can get much more information about the event in this RIPE Labs article: https://labs.ripe.net/Members/becha/lets-deploy-together-ripe-atlas-softwar… Feel free to share it with your local communities and hopefully we’ll see you all on 25 November! Kind regards, Lia Hestina RIPE NCC _________

1 0

Result processing glitch
by Robert Kisteleki 12 Oct '20

12 Oct '20

Dear RIPE Atlas users, Today one of our controllers (a component that handles probes and deals with their submitted results) was updated to run a new version of result processing code. Unfortunately this code had a bug that caused results to be mixed up. As a result, some of the results that were delivered by this controller were of the wrong type / syntax, which may result in errors in processing this data. We reverted this change as soon as we detected the error. This issue likely affected results delivered by about 2% of our probes, between 13:30 and 15:15 (CEST). We apologise for the inconvenience. Regards, Robert Kisteleki RIPE NCC

1 0

Latest software version for v3 probe
by Ashu 06 Oct '20

06 Oct '20

Hi My v3 probe 25250 has software version firmware version 4900(1100). However, i have seen other v3 probe on version 5020(1100). Why my probe is not updated to the latest version automatically. Is there a way i can update my probe to latest firmware version. Regards, Ashu

1 0

Re: [atlas] ripe-atlas Digest, Vol 109, Issue 11
by Florian Rohde 24 Sep '20

24 Sep '20

10 million points have just been added to the Research Concern. I wish you success. Cheers, Florian Florian Rohde Neue Landbuch GmbH & Co. KG Telefon: +49 4231 9552-79 Fax: E-Mail: Florian.Rohde(a)nlb.de --------------------------------------------------------------------------------- Neue Landbuch Gesellschaft m.b.H Gesellschaft für moderne Datenverarbeitung & Co. KG Heinrich-Schröder-Weg 1 27283 Verden Telefon: +49 4231 9552-0 Fax: +49 4231 9552-66 E-Mail: info(a)nlb.de Internet: www.nlb.de Kommanditgesellschaft mit Sitz in Verden Registergericht Walsrode, HRA 121111 Pers. haftender Gesellschafter: Neue Landbuch GmbH, Verden Geschäftsführer: Bernhard Kramer Aufsichtsratsvorsitzender: RA StB Ralf Stephany -----Ursprüngliche Nachricht----- Von: ripe-atlas [mailto:ripe-atlas-bounces@ripe.net] Im Auftrag von ripe-atlas-request(a)ripe.net Gesendet: Donnerstag, 24. September 2020 12:00 An: ripe-atlas(a)ripe.net Betreff: ripe-atlas Digest, Vol 109, Issue 11 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. Re: Request for credits for research (Ponikierski, Grzegorz) ---------------------------------------------------------------------- Message: 1 Date: Thu, 24 Sep 2020 09:46:45 +0000 From: "Ponikierski, Grzegorz" <gponikie(a)akamai.com> To: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi>, "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: Re: [atlas] Request for credits for research Message-ID: <EEB33D82-5DC6-481B-89B0-C11B6FB52EC6(a)akamai.com> Content-Type: text/plain; charset="utf-8" 50M from me. Waiting for paper ;) Regards, Grzegorz From: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi> Date: Thursday 2020-09-24 at 00:02 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Request for credits for research Dear RIPE community, I hope you are all safe and sound. I am a Postdoctoral fellow at the Technical University of Munich, Germany. We are currently working on an ongoing research project which aims to analyze the availability and reachability of cloud data centers globally. The first work of our work will appear in ACM HotNets 2020 titled "Pruning Edge Research with Latency Shears" (http://conferences.sigcomm.org/hotnets/2020/program.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__conferences.sigcomm.org…>). We are currently preparing the camera-ready version of the paper and will share it with the community by hosting it (and the associated dataset) publicly soon. We are currently planing to submit the second leg of our work to a conference with submission deadline a month. In order to complete all set of measurements for required analysis, we are scheduling very large-scale measurements over the platform which has burned through almost all our credits and left us in need. I have always found the RIPE Atlas community to be helpful and generous towards research and I am hoping that you could support our research by donating us some of your spare credits. Your help will be highly appreciated. My RIPE account is nitinder.mohan(a)helsinki.fi Thanks and Regards Nitinder Mohan Postdoctoral Fellow Technical University of Munich, Germany https://www.nitindermohan.com/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.nitindermohan.com_…>

1 0

Re: [atlas] Request for credits for research
by Ponikierski, Grzegorz 24 Sep '20

24 Sep '20

50M from me. Waiting for paper ;) Regards, Grzegorz From: "Mohan, Nitinder" <nitinder.mohan(a)helsinki.fi> Date: Thursday 2020-09-24 at 00:02 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Request for credits for research Dear RIPE community, I hope you are all safe and sound. I am a Postdoctoral fellow at the Technical University of Munich, Germany. We are currently working on an ongoing research project which aims to analyze the availability and reachability of cloud data centers globally. The first work of our work will appear in ACM HotNets 2020 titled "Pruning Edge Research with Latency Shears" (http://conferences.sigcomm.org/hotnets/2020/program.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__conferences.sigcomm.org…>). We are currently preparing the camera-ready version of the paper and will share it with the community by hosting it (and the associated dataset) publicly soon. We are currently planing to submit the second leg of our work to a conference with submission deadline a month. In order to complete all set of measurements for required analysis, we are scheduling very large-scale measurements over the platform which has burned through almost all our credits and left us in need. I have always found the RIPE Atlas community to be helpful and generous towards research and I am hoping that you could support our research by donating us some of your spare credits. Your help will be highly appreciated. My RIPE account is nitinder.mohan(a)helsinki.fi Thanks and Regards Nitinder Mohan Postdoctoral Fellow Technical University of Munich, Germany https://www.nitindermohan.com/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.nitindermohan.com_…>

1 0

Invalid results in TraceMON tool
by Andreas Siskos 09 Sep '20

09 Sep '20

Hello everyone, I am an undergraduate student at University of Crete and as a part of my bachelor thesis, I am trying to integrate TraceMON in a website. I used the example code that it was provided by the web page of TraceMON in RIPE Atlas website ( https://atlas.ripe.net/docs/tools-tracemon/#embed), but I noticed something unexpected. The graph of the TraceMON was not taking the same path as the raw data of traceroutes. There were the right destinations/IPs, but in shuffled order. Let's consider the example of measurement ID 26813196. As you can see, in the raw data of the traceroute ( https://atlas.ripe.net/api/v2/measurements/26813196/results/), it reaches the target IP (103.83.160.1) at 16th hop from probe 55564. When I checked the graph in TraceMON on the RIPE Atlas website ( https://atlas.ripe.net/measurements/26813196/#!tracemon) (see attached: general.png), the traceroute from probe 55564 was represented in the picture graph.png. As you can see in the data file data.png, the destination IP was reached at 3rd hop instead of 16th, that was in the raw data of the traceroute. The same behavior can be observed for the probes 19648 and 32788. Am I missing something? Thank you in advance, Andreas Siskos

1 0

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

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

New on RIPE Labs: What’s the Deal with IPv6 Link-Local Addresses?
by Philip Homburg 11 Mar '20

11 Mar '20

Dear colleagues, Stephen Strowes, Emile Aben and I published a new article on RIPE Labs on how link-local addresses in IPv6, and specifically the '%eth0'-part of link-local addresses, can have an impact on RIPE Atlas measurements. https://labs.ripe.net/Members/philip_homburg/whats-the-deal-with-ipv6-link-… We think this will be an interesting read for network operators and others who are using RIPE Atlas measurement data or are interested in IPv6. Kind regards, Philip Homburg RIPE NCC

1 0

Broken traffic graphs in latest firmware (5010)
by Philip Homburg 10 Mar '20

10 Mar '20

Hi, A change in the RIPE Atlas probe code to make reporting traffic statistics optional in software probes (and disabled by default) has the unfortunate side-effect that reporting of traffic statistics is now disabled on Version 3 and Version 4 hardware probes, as well as all anchors. This change was rolled out in firmware version 5010. Unfortunately, this effect was not spotted during testing. We will roll out a new firmware release that corrects this issue in coming weeks. Philip

1 0