- ripe-atlas - mailman.ripe.net

Probe on OpenWRT does not load telnetd
by Ernst J. Oud 30 Jun '22

30 Jun '22

Just a tip for OpenWRT users. I noticed that during most reboots my new SW probe on OpenWRT 21.02 does not load the telnetd daemon. No idea why but I saw that its priority in init.d is rather high (S30), i.e. it loads rather early. Perhaps that is the problem but instead I test for telnetd running in the ATLAS loop and load the daemon if not. Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud > On 30 Jun 2022, at 12:00, 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. Re: Overuse of software probes (Emile Aben) > 2. Re: Probe on sailboat with Starlink (Daniel Karrenberg) > 3. Re: Assigned AS vs. Advertising AS (ripe.net(a)toppas.net) > 4. Re: Overuse of software probes (Romain Fontugne) > 5. RIPE Atlas Quarterly Planning Q3 2022 (Robert Kisteleki) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 29 Jun 2022 14:34:08 +0200 > From: Emile Aben <emile.aben(a)ripe.net> > To: "Ponikierski, Grzegorz" <gponikie(a)akamai.com>, RIPE Atlas > <ripe-atlas(a)ripe.net> > Subject: Re: [atlas] Overuse of software probes > Message-ID: <7f053467-59c6-69e0-6a33-44a1b42efdd2(a)ripe.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > >> Emile Aben, I would be happy to see code for detecting overly similar >> probes. It would save a lot of time spend on data filtering. > > These are snapshots of data for probe similarity detection [1] in IPv4 > and IPv6 > > https://sg-pub.ripe.net/emile/probe-similarity/probe_similarity_ipv4-2022-0… > https://sg-pub.ripe.net/emile/probe-similarity/probe_similarity_ipv6-2022-0… > > This calculates 3 similarity values between 0 and 1 (the last 3 values > in the csv). Pick the middle one if you don't care about the details. > > There are 54k probe-pairs with similarity values over 0.5, > 7.4k with value over 0.95 > 6.7k with value over 0.99 > > My gut feeling is that anything over 0.95 is likely very redundant for > many types of measurements. > > There seems to be a cluster of about 400 probes that are very similar to > each other, and a couple of smaller clusters too. > > Happy to work with you and others to see if we can make this into > something that is operationally valuable. > > kind regards, > Emile Aben > RIPE NCC > > [1] Holterbach, Thomas, et al. "Measurement vantage point selection > using a similarity metric." Proceedings of the Applied Networking > Research Workshop. 2017. > https://trac.ietf.org/trac/irtf/export/478/www/content/anrw/2017/anrw17-fin… > > > > > ------------------------------ > > Message: 2 > Date: Wed, 29 Jun 2022 14:46:26 +0200 > From: Daniel Karrenberg <dfk(a)ripe.net> > To: Stephen Strowes <s(a)sdstrowes.co.uk>, ripe-atlas(a)ripe.net > Subject: Re: [atlas] Probe on sailboat with Starlink > Message-ID: <2df11fd5-5385-ee11-e5fc-ded5839a6beb(a)ripe.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > > >> On 28-06-2022 19:46, Stephen Strowes wrote: >> ... I have no idea how starlink decides what ground station to bounce >> your service down onto, it might be interesting to see how it works >> the further you get from home. > > https://starlink.sx/ is a nice *simulation* that provides some graphical > insight in what POPs might be used and why. > NB: one can set the user location at the top right. > > Daniel > > PS: Receiving my starlink RV in a few days. I will test it at home > first. If there is a spare probe, I'll be happy to connect it later. > > > > ------------------------------ > > Message: 3 > Date: Wed, 29 Jun 2022 18:05:44 +0200 > From: ripe.net(a)toppas.net > To: Gert Doering <gert(a)space.net> > Cc: ripe-atlas(a)ripe.net > Subject: Re: [atlas] Assigned AS vs. Advertising AS > Message-ID: <9049c43c-8f51-8710-9061-6ce680a83eeb(a)toppas.net> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Gert, > > thanks for your clarification! But you still get my point, do you? > If a prefix was assigned to an entity other than the one that is advertising the prefix, for example: 80.187.128.0/22 > > Announcing: Deutsche Telekom AG (AS3320) > Assigned: T-Mobile Deutschland GmbH (AS44178) > > The information (original prefix receiver) is stored in the RIPE DB, right? It could be compared to what we see via BGP. > I am aware that a single entity can have multiple AS numbers, but when different entities are "involved", more transparency would be great. > > Or am i missing something here? > > BR, > Simon > >> On 29.06.22 10:54, Gert Doering wrote: >> Hi, >>> On Wed, Jun 29, 2022 at 10:30:22AM +0200, Simon Brandt via ripe-atlas wrote: >>> Another example would be a multi ASN company which announces all >>> prefixes from a single ASN via BGP, even though the prefixes are >>> assigned to various AS numbers. Since the RIRs do have the information, >>> to which AS a specific prefix is assigned to, >> prefixes are not assigned to "AS" numbers, ever. >> prefixes are assigned to entities, as are AS numbers. >> ROAs and/or route(6): objects are used to tie both together - and it's >> in the authority of the network (prefix) holder to state which AS is >> allowed and expected to announce a given prefix, not the RIR. >> Repeat: the RIR has no say in "which AS is tied a prefix". >> Gert Doering >> -- NetMaster >

1 0

RIPE Atlas Quarterly Planning Q3 2022
by Robert Kisteleki 30 Jun '22

30 Jun '22

Dear colleagues, The quarterly plans for RIPE Atlas can now be found at: https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas In this quarter, we will continue with the development of the v5 RIPE Atlas hardware probes among other items as well as start working on two proposals to implement general availability of HTTP measurements and restricting the ability to schedule "non-public measurements". The goal of our quarterly planning is to communicate the work we’re doing for the coming months, get your input and start a discussion on other developments we should work on. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC

1 0

Assigned AS vs. Advertising AS
by ripe.net＠toppas.net 29 Jun '22

29 Jun '22

Hi Everyone, worldwide, there are a lot of IP prefixes which are not advertised by the owner AS. Instead, another AS announces the prefix on behalf of the owner. For example: Amazon allows you to announce your prefix via AWS. For other people, this can lead to misassumptions (assuming a wrong IP owner). https://aws.amazon.com/about-aws/whats-new/2018/10/announcing-the-general-a… Another example would be a multi ASN company which announces all prefixes from a single ASN via BGP, even though the prefixes are assigned to various AS numbers. Since the RIRs do have the information, to which AS a specific prefix is assigned to, i would like to ask for more transparency. I would appreciate, if we could see more details here, and even more important: filter for such criterias when creating a new measurement. Anyone else here, who thinks that's useful? BR, Simon

2 2

DNS issues
by Phillip Remaker 29 Jun '22

29 Jun '22

I have installed a probe (/14226) at a rural fixed wireless location which has had intermittent issues from the carrier (AT&T). I got the tag about a DNS issue (Doesn't Resolve A, DNS Problem Suspected). Is it possible to get logs for when the DNS issue happened so I can take it up with the carrier? Also, when does the DNS problem tage clear? Thanks!

3 2

Credits Request
by Martin, Noah S 29 Jun '22

29 Jun '22

Hi all, I’m a new PhD student at Tufts University in Boston, and I'm starting to work on a cloud latency project. If anyone has credits to spare, donations would be greatly appreciated! My account is noah.martin(a)tufts.edu<mailto:noah.martin@tufts.edu> 100k credits would be perfect to get started on my experiments. Thanks, Noah Martin

8 8

Re: [atlas] Credits Request
by Marc Goldburg 28 Jun '22

28 Jun '22

Hi Noah, Just transferred 1m credits. Good luck and please share results when possible. Marc

1 0

Re: [atlas] ripe-atlas Digest, Vol 130, Issue 15
by ignacio.leon 28 Jun '22

28 Jun '22

Hi Noah, 1 Million credits transferred to you. Good luck with your research cheers -- Ignacio Leon Halcyon Pin Mill Rd IP9 1JN Suffolk United Kingdom ignacio.leon(a)yleon.com Mobile: +44 (0) 782 614 5208 On 28.06.2022 21:22, 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. Re: Credits Request (Nick Hilliard) > 2. Re: Credits Request (David Prall) > 3. Re: Credits Request (Martin, Noah S) > 4. Re: Credits Request (Fadloe Robby) > 5. Re: Credits Request (Rich Smith) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 Jun 2022 19:45:13 +0100 > From: Nick Hilliard <nick(a)foobar.org> > To: "Martin, Noah S" <Noah.Martin(a)tufts.edu> > Cc: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> > Subject: Re: [atlas] Credits Request > Message-ID: <2096ae3c-bbb8-769b-41a7-889d1bc0996c(a)foobar.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Martin, Noah S wrote on 28/06/2022 19:42: > >> I?m a new PhD student at Tufts University in Boston, and I'm starting >> to >> work on a cloud latency project. If anyone has credits to spare, >> donations would be greatly appreciated! My account is >> noah.martin(a)tufts.edu <mailto:noah.martin@tufts.edu>?100k credits >> would >> be perfect to get started on my experiments. > > just transferred 10m - just drop an email to the atlas community if you > need any more. And we'd love to see any outcomes! > > Nick > > ------------------------------ > > Message: 2 > Date: Tue, 28 Jun 2022 15:44:13 -0400 > From: David Prall <dcp(a)dcptech.com> > To: ripe-atlas(a)ripe.net > Subject: Re: [atlas] Credits Request > Message-ID: <1de5dfeb-d68f-79aa-f44e-9da972d8a9dc(a)dcptech.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Noah, > Did the same 10 million > > David > > -- > https://dprall.net > > On 6/28/2022 2:45 PM, Nick Hilliard wrote: Martin, Noah S wrote on > 28/06/2022 19:42: I?m a new PhD student at Tufts University in Boston, > and I'm starting > to work on a cloud latency project. If anyone has credits to spare, > donations would be greatly appreciated! My account is > noah.martin(a)tufts.edu <mailto:noah.martin@tufts.edu>?100k credits > would be perfect to get started on my experiments. > just transferred 10m - just drop an email to the atlas community if you > need any more.? And we'd love to see any outcomes! > > Nick ------------------------------ Message: 3 Date: Tue, 28 Jun 2022 19:45:55 +0000 From: "Martin, Noah S" <Noah.Martin(a)tufts.edu> To: Nick Hilliard <nick(a)foobar.org> Cc: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: Re: [atlas] Credits Request Message-ID: <8799C872-A640-4C49-9F23-88E136FE7002(a)tufts.edu> Content-Type: text/plain; charset="utf-8" Thanks so much! > On Jun 28, 2022, at 2:45 PM, Nick Hilliard <nick(a)foobar.org> wrote: > > Martin, Noah S wrote on 28/06/2022 19:42: > >> I?m a new PhD student at Tufts University in Boston, and I'm starting >> to work on a cloud latency project. If anyone has credits to spare, >> donations would be greatly appreciated! My account is >> noah.martin(a)tufts.edu <mailto:noah.martin@tufts.edu> 100k credits >> would be perfect to get started on my experiments. > > just transferred 10m - just drop an email to the atlas community if you > need any more. And we'd love to see any outcomes! > > Nick ------------------------------ Message: 4 Date: Wed, 29 Jun 2022 04:19:07 +0800 From: Fadloe Robby <frobby(a)ulm.ac.id> To: "Martin, Noah S" <Noah.Martin(a)tufts.edu> Cc: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: Re: [atlas] Credits Request Message-ID: <CADRCOtH42Bokrge+9cBJfsuQYKR7n5LDX4Gyy34aUToqVy1_sw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Noah Martin, I just sent you 30 million. Good luck with your research cloud latency project , and let us know if you need any more I'm sure many others will send you much more over the coming days. Pada tanggal Rab, 29 Jun 2022 pukul 02.42 Martin, Noah S < Noah.Martin(a)tufts.edu> menulis: > Hi all, > > I?m a new PhD student at Tufts University in Boston, and I'm starting > to > work on a cloud latency project. If anyone has credits to spare, > donations > would be greatly appreciated! My account is noah.martin(a)tufts.edu 100k > credits would be perfect to get started on my experiments. > > Thanks, > Noah Martin > > -- > ripe-atlas mailing list > ripe-atlas(a)ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas -- Thank you for your consideration. Best regards, Fadloe Robby Telp/WA : 0812-5154-3201 Univeritas Lambung Mangkurat UPT PTIK Univeritas Lambung Mangkurat gedung Rektorat Lantai III Jalan Brigjen H. Hasan Basri Banjarmasin 70123 Telp./Fax. (0511) 330 5195,

1 0

Meaning behind "TU_BAD_ADDR" error
by Meikel Kokowski 22 Jun '22

22 Jun '22

Good evening, While parsing data from some of my measurements (using ripe.atlas.sagan) I stumbled over the “TU_BAD_ADDR” error. The error message is only “true” which makes it difficult to understand its origin. Furthermore, as opposed to other errors, such as “timeout”, no error is indicated by the is_error method of the DnsResult object. Instead I can only find this in the raw_data (in the dns respone object). In my measurements I send the same DNS query (using probe’s IPv6-address) to public resolver and the probes local resolver over UDP and TCP respectively. The TU_BAD_ADDR error occurred solely on measurements to the probes local resolver over TCP. Respective measurements using the same probes over UDP do not report this error. Another observation is that the source address of the response is not set in the majority of the cases (but that is not always the case). An example measurement is #41853554 (the counter-measurement over UDP #41853806). Does anyone know more about this? Best regards, Meikel

1 0

RIPE Atlas down?
by Ernst J. Oud 22 Jun '22

22 Jun '22

Hi, I noticed that of the probes I checked here in The Netherlands, all logging stops at around 03:00 today (June, 22nd). Checked a probe in Germany, same thing but stopped a couple of hours later it seems. Is there some problem? Regards, Ernst J. Oud > On 21 Jun 2022, at 12:00, 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. Re: No data for ping to second hop? (Ernst J. Oud) > 2. Re: No data for ping to second hop? (Ponikierski, Grzegorz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 20 Jun 2022 19:09:01 +0200 > From: "Ernst J. Oud" <ernstoud(a)gmail.com> > To: ripe-atlas(a)ripe.net > Subject: Re: [atlas] No data for ping to second hop? > Message-ID: <E7C26305-00C5-4527-9FE1-F0534352F82E(a)gmail.com> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > Thanks for the reply. But it appears to be a common problem for Linux containers in Docker Desktop for Windows. All traceroute commands only show asterisks. As explained here: > > https://github.com/moby/vpnkit/pull/302 > > (vpnkit is used by Docker in Windows). > > So I will have to install the probe in a native Linux environment instead. > > Which raises another question: if I get the probe running in native Linux, can I transfer my current probe ID to this new installation? Or do I have to apply for a new probe (and disconnect the other)? > > Regards, > > Ernst > >> On 20 Jun 2022, at 12:00, ripe-atlas-request(a)ripe.net wrote: >> >> Re: No data for ping to second hop? >

3 2

Re: [atlas] No data for ping to second hop?
by Ernst J. Oud 20 Jun '22

20 Jun '22

Hi, Thanks for the reply. But it appears to be a common problem for Linux containers in Docker Desktop for Windows. All traceroute commands only show asterisks. As explained here: https://github.com/moby/vpnkit/pull/302 (vpnkit is used by Docker in Windows). So I will have to install the probe in a native Linux environment instead. Which raises another question: if I get the probe running in native Linux, can I transfer my current probe ID to this new installation? Or do I have to apply for a new probe (and disconnect the other)? Regards, Ernst > On 20 Jun 2022, at 12:00, ripe-atlas-request(a)ripe.net wrote: > > Re: No data for ping to second hop?

2 1

No data for ping to second hop?
by Ernst J. Oud 19 Jun '22

19 Jun '22

Hi, Out of curiosity, all my “Built-ins” in my software probe show data except ”#2 Second Hop to ping.ripe.net (193.0.0.164)” which shows: “No data available for [Probe ID] / 2 for this time period.” Any advice? Regards, Ernst Update: This appears to be a docker for Windows issue. My software probe runs on Alpine Linux in docker on Windows 10 WSL. Investigating further…

2 1

No data for ping to second hop?
by Ernst J. Oud 17 Jun '22

17 Jun '22

Hi, Out of curiosity, all my “Built-ins” in my software probe show data except ”#2 Second Hop to ping.ripe.net (193.0.0.164)” which shows: “No data available for [Probe ID] / 2 for this time period.” Any advice? Regards, Ernst

1 0

Discrepancy in documentation?
by Stephane Bortzmeyer 09 Jun '22

09 Jun '22

[Message already sent on 6 june but it never appeared in my mailbox. Is there some email problem at RIPE?] In the documentation <https://beta-docs.atlas.ripe.net/apis/metadata-reference/>, various HTTP methods are used (for instance DELETE to delete a measurement), which is nice, but the examples ("Try it") always show the method GET.

2 1

How to get DNS return codes and TTLs
by Dallan Adamson 09 Jun '22

09 Jun '22

I'm doing research that requires me to use DNS recursive resolvers around the world. At a minimum from these recursive resolvers I need to know what return code the probe received from the recursive resolver as well as the TTL of the record from the same request. I haven't found a way to get both of these when doing DNS measurements with Ripe Atlas probes, is there a way to do this?

2 1

Future of Software Anchors
by Lukas Magauer 03 Jun '22

03 Jun '22

Hi everybody! I have been running a Software probe on CentOS 8 since mid 2020. (and since switched it to Rocky Linux 8) It’s unsupported, but also didn’t really make any problems, just worked fine with the yum repo distributed package! Great that there are already plans to support newer versions as well! And has there something changed in the distribution of the package? Because the latest changes of version 5070 don’t look like they appeared in the GitHub repo? Best regards, Lukas On 14/05/2022 11:14, ripe.net--- via ripe-atlas wrote: Hi Simon, > So it does not really make sense, to set up a new Anchor with CentOS 7, > i guess. What are the plans, dear RIPE Labs? > I searched the atlas mailinglist topics for "software anchor" and > "centos 7" but didn't find anything. For now, we are still deploying Atlas anchors with CentOS 7. However, in the latter half of this year, we plan to work on adapting our configuration systems to a newer Linux distribution. After that, we will upgrade all the Atlas anchors (hardware and virtual) to the newer distribution. Regards, Anand Buddhdev RIPE NCC Hi everyone, accoring to this site, a CentOS 7 installation is required for running a Software Anchor: https://atlas.ripe.net/docs/anchor-installation-vm/ But CentOS 7 will be End-of-Lifetime in two years (30. Juni 2024). https://wiki.centos.org/About/Product So it does not really make sense, to set up a new Anchor with CentOS 7, i guess. What are the plans, dear RIPE Labs? I searched the atlas mailinglist topics for "software anchor" and "centos 7" but didn't find anything. Greetings, Simon

3 3

Re: [atlas] Ongoing problem with DoT measurements
by Michel Stam 31 May '22

31 May '22

Hi Meikel, Sorry for the silence. I had noticed your issue and apparently forgot to reply we were looking into it. As it is we are, bear with us, I will respond as soon as we have an update. Regards, Michel > On 31 May 2022, at 12:19, Meikel Kokowski <meikel.kokowski(a)stud.uni-hannover.de> wrote: > > Does really no one have any idea or thought concerning this problem? > Anything would be appreciated! > > From: Meikel Kokowski <mailto:meikel.kokowski@stud.uni-hannover.de> > Sent: Tuesday, 24 May 2022 02:48 > To: ripe-atlas(a)ripe.net <mailto:ripe-atlas@ripe.net> > Subject: [atlas] Ongoing problem with DoT measurements > > Dear RIPE Mailing List, > > in the context of my final thesis I am conducting research related to DNS (Do53 and DoT) using RIPE Atlas probes. In preparation for the main measurement I issued, to around 4800 probes, DNS queries > > 1) over TLS [measurement ID: 41196896] and > 2) over Do53 (standard) [measurement ID: 41196980] > > While Do53 works perfectly, DoT seems not to yield any results at all. In the RIPE Atlas forum I found a similar question (https://www.ripe.net/participate/mail/forum/ripe-atlas/PDIwMjIwMzI0MTIzMzE1…). According to that thread, a configuration error on the probes causes the problem. That post is 2 months ago and the problem seems to subsist. Could you provide an update to the current situation to this problem and a possible date for a fix? > > Thank you! > > Best, > Meikel > > -- > ripe-atlas mailing list > ripe-atlas(a)ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas

1 0

Re: [atlas] Ongoing problem with DoT measurements
by Meikel Kokowski 31 May '22

31 May '22

Does really no one have any idea or thought concerning this problem? Anything would be appreciated! From: Meikel Kokowski Sent: Tuesday, 24 May 2022 02:48 To: ripe-atlas(a)ripe.net Subject: [atlas] Ongoing problem with DoT measurements Dear RIPE Mailing List, in the context of my final thesis I am conducting research related to DNS (Do53 and DoT) using RIPE Atlas probes. In preparation for the main measurement I issued, to around 4800 probes, DNS queries 1) over TLS [measurement ID: 41196896] and 2) over Do53 (standard) [measurement ID: 41196980] While Do53 works perfectly, DoT seems not to yield any results at all. In the RIPE Atlas forum I found a similar question (https://www.ripe.net/participate/mail/forum/ripe-atlas/PDIwMjIwMzI0MTIzMzE1…). According to that thread, a configuration error on the probes causes the problem. That post is 2 months ago and the problem seems to subsist. Could you provide an update to the current situation to this problem and a possible date for a fix? Thank you! Best, Meikel

1 0

AS34659
by Jacques Lavignotte 29 May '22

29 May '22

Hi, I may be wrong but it looks like there are 3 probes at ASN34659 (Keyyo) and only 1 is up ? Can anyone confirm ? Thanks, Jacques -- GnuPg : 156520BBC8F5B1E3 Because privacy matters. « Quand est-ce qu'on mange ? » AD (c) (tm)

2 1

Looking for a hardware probe
by Giuseppe Macario 25 May '22

25 May '22

Hello everyone, I would like to host a new Atlas probe (for AS203591) but I understand that RIPE is not shipping probes anymore; I applied online but nobody responded. Therefore, feel free write me an email if you have one for sale, in which case I am willing to pay via PayPal. I will also ask RIPE for a new probe ID, so the history attached to your old probe will be reset. PS: not interested in software probes. -- Giuseppe Macario, PhD https://giuseppemacario.men https://www.giuseppemacario.it

5 4

RIPE-Atlas measurements showed "No recent report available"
by Tingting Lu 25 May '22

25 May '22

Hi all, I am using RIPE-Atlas to generate some ping measurements for my testing ip recently. It worked very well until yesterday. Starting from May 23rd, most of my measurements only have results for a few probes. Most probes showed "No recent report available". Does anyone have the same problem or know what's going on there? -- Regards, Tingting Lu

3 3

RIPE-Atlas measurements showed "No recent report available" [DUP]
by POULET Benoit 25 May '22

25 May '22

Hello, Sorry i can't reply to the already started thread as i'm a new subscriber. I can confirm the problem. I have a lot of measurements with "No recent report available" For examples : https://atlas.ripe.net/measurements/41368751/ https://atlas.ripe.net/measurements/41368760/ https://atlas.ripe.net/measurements/41368768/ It's stared from (UTC+2h) : May 23, 2022 11:28:57 AM

1 0

Ongoing problem with DoT measurements
by Meikel Kokowski 23 May '22

23 May '22

Dear RIPE Mailing List, in the context of my final thesis I am conducting research related to DNS (Do53 and DoT) using RIPE Atlas probes. In preparation for the main measurement I issued, to around 4800 probes, DNS queries 1) over TLS [measurement ID: 41196896] and 2) over Do53 (standard) [measurement ID: 41196980] While Do53 works perfectly, DoT seems not to yield any results at all. In the RIPE Atlas forum I found a similar question (https://www.ripe.net/participate/mail/forum/ripe-atlas/PDIwMjIwMzI0MTIzMzE1…). According to that thread, a configuration error on the probes causes the problem. That post is 2 months ago and the problem seems to subsist. Could you provide an update to the current situation to this problem and a possible date for a fix? Thank you! Best, Meikel

1 0

Probe TLS stack
by Christopher Wood 15 May '22

15 May '22

Hi folks, Apologies in advance if the answer to this question is available online somewhere, but I’m wondering if anyone knows what TLS stack is used in Atlas probes, and in particular, what sort of TLS features are configurable by such probes. Best, Chris

2 2

Future of Software Anchors
by ripe.net＠toppas.net 15 May '22

15 May '22

Hi everyone, accoring to this site, a CentOS 7 installation is required for running a Software Anchor: https://atlas.ripe.net/docs/anchor-installation-vm/ But CentOS 7 will be End-of-Lifetime in two years (30. Juni 2024). https://wiki.centos.org/About/Product So it does not really make sense, to set up a new Anchor with CentOS 7, i guess. What are the plans, dear RIPE Labs? I searched the atlas mailinglist topics for "software anchor" and "centos 7" but didn't find anything. Greetings, Simon

3 2

Atlas probes, IPv6, EUI-64, and privacy
by Alexander Burke 03 May '22

03 May '22

Hello all, I couldn't help but notice that my Atlas probe is using an EUI-64 IPv6 address. It has come to light that the presence of even one device using an EUI-64 address on a network has a negative effect on privacy for the whole network: https://arxiv.org/abs/2203.08946 Thoughts? Cheers and thanks in advance, Alex

2 1

My probe's not doin' IPv6
by Edward Lewis 23 Apr '22

23 Apr '22

General question… My probe was doing IPv6 until 15 July 2021 but not it is not. Is there any way to discover why it is no longer IPv6’ing? I did change my ISP connection equipment about that time, so something did change on my end. But IPv6 works for other devices. When I go to www.ripe.net <http://www.ripe.net/> it tells me I came from an IPv6 address. The device has been pretty steady - 99.71% the last week, 99.91% for the last month (30days). It was off-line 29 minutes earlier today (the notice made me think to look), but never off line more than 10 minutes since mid-July. There’s one stretch of 34d+ of continuous uptime. Run-of-the-mill home connection via a cableTV company. Is there anyway to ask a probe why it doesn’t have an IPv6 address (via DHCP)? Ed

5 7

TLSv1.3 Support
by Antonios Chariton 23 Apr '22

23 Apr '22

I’ve ran a measurement against a host that only support TLSv1.3 ( https://atlas.ripe.net/measurements/40393656/#probes ) and all probes came back with "Error: protocol_version”. Do they not support the latest version of TLS? I only seem to be able to get them to work with TLSv1.2 or lower. Thanks, Antonios

1 0

json with all probes
by Cristel Pelsser 23 Apr '22

23 Apr '22

Hi, Can someone point me to the location of the json file with all the probes and their properties? Cristel

2 2

Moving on
by Philip Homburg 06 Apr '22

06 Apr '22

Hi Atlas Users, After ten years at the RIPE NCC it is time for me to move on. Normally, that is not something that would be announced on a public mailing list. However, I get quite a bit of email that is directly sent to me. This is to let you know that I will not be able to read future email sent to this address. I have two new colleagues who will work on probe firmware development. They are Guy Meyer <gmeyer(a)ripe.net> and Michel Stam <mstam(a)ripe.net>. I'm sure they will be happy to help. As for me, I will be <philip(a)nlnetlabs.nl> from now on. Philip Homburg

3 2

RIPE Atlas Quarterly Planning Q2 2022
by Robert Kisteleki 31 Mar '22

31 Mar '22

Dear colleagues, We are now publishing our quarterly planning for RIPE Atlas. This is available at: https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas The goals of publishing our planning are to be transparent about the work we will be carrying out in the coming months, to get your input on those plans, and hear what you would like to see the RIPE NCC work on going forward. We will provide status updates as the work progresses and add input from the community to the pages. We will also archive previous plans so you can track how we progress with our work. If you have any input on our plans or want to let us know what you would like to see us work on, please let us know. Kind regards, Robert Kisteleki Research and Development Manager RIPE NCC

1 0

New on RIPE Labs: Bias in Internet Measurement Infrastructure
by Alun Davies 28 Mar '22

28 Mar '22

Dear colleagues, In this new article on RIPE Labs, Pavlos Sermpezis talks about analysing bias in the Internet measurement infrastructures like RIPE Atlas and RIPE RIS. Are these infrastructures biased? How much of a problem is it if they are? What does bias even look like here? Find out more: https://labs.ripe.net/author/pavlos_sermpezis/bias-in-internet-measurement-… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

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 18 Feb '22

18 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