- ripe-atlas - mailman.ripe.net

My experiences with a SW probe…
by Ernst J. Oud 05 Jul '22

05 Jul '22

Don’t know whether this is the place to share experiences but … I installed a SW probe in Docker for Windows (the Alpine version). Turns out traceroute doesn’t work in that setup. So I installed VMware player on that PC (the latest version can coexist with Hyper-V which Docker requires) and CentOS and the binary of the probe. Of which the instructions on the Ripe Atlas site doesn’t work in the last step (yum complains no package atlasswprobe found in the repo). Manual download and install did work however. Hurrah. Turns out traceroute in that setup only works with VMware in bridged network mode. Fine. But… all my bandwidth tests on that same box suddenly showed strange impacts… so either a working probe and accept incorrect bandwidth tests (using Ookla SpeedTest) or find another solution. Apparently the bridge in VMware and Windows on the same physical Ethernet port influence each other. Tried the probe on OpenWRT on a small router. Works fine but I don’t want to dedicate this router to just probe work. Also the ATLAS service from init.d refuses to run the telnetd daemon at startup. Weird. So installed VMware on a separate Windows 10 headless box (Minix Z83) that I had spare with CentOS and the binary. Runs fine. Finally. Will kill the other two probes once I am convinced it now finally works. Thanks Ripe for this excellent tool! A Windows version would help however :-) Regards, Ernst

2 1

Connectivity Issue - Software Probe ID 1002750
by Thomas Kessler 02 Jul '22

02 Jul '22

Hi there, a software probe of mine - ID 1002750 - has stop working about 30 days ago and I seem not to be able to get it to connect again. tcpdump shows plenty of communication between the probe and reg03 / reg04.atlas.ripe.net. As well, the probe sending SOS DNS queries but neither seem to have any effect. RIPE Atlas Console shows the probe as being descended and the SOS DNS queries are not reported there either. I've check the probes registered public key and there should be no issue. Any ideas? Best regards Thomas

1 0

Overuse of software probes
by Ponikierski, Grzegorz 30 Jun '22

30 Jun '22

Hello all! Software probes is great improvement for Atlas environment and it made deployments so much easier and more scalable. One of my probes is also software probe on Raspberry Pi. However, me and my team noticed that sometimes software probes are overused and make measurements more cumbersome to interpret. For example we found that there 4 software probes in AWS Johannesburg [1] and 15 software probes in Hostinger Sao Paulo [2]. That's total overkill. These 15 probes in Hostinger Sao Paulo is 21% of all connected probes in Brazil. All of them delivers practically the same results so without additional data filtering (which is not easy) they can dramatically skew final results for Brazil. With this I would like to open discussion how to handle this situation. Please share your thoughts about these questions: * How can we standardize data filtering for such case? * How to proactively and automatically detect overuse of probes? * How can we encourage software probes hosts to avoid deployments in data centers which are already covered by Atlas? * How to give incentives to deploy probes in data centers without existing probes? [1] 4 software probes inside AWS Johannesburg: 1000707<https://atlas.ripe.net/frames/probes/1000707/> 1001397<https://atlas.ripe.net/frames/probes/1001397/> 1002066<https://atlas.ripe.net/frames/probes/1002066/> 1002632<https://atlas.ripe.net/frames/probes/1002632/> [2] 15 software probes inside Hostinger Sao Paulo 1003554<https://atlas.ripe.net/frames/probes/1003554/> 1003555<https://atlas.ripe.net/frames/probes/1003555/> 1003556<https://atlas.ripe.net/frames/probes/1003556/> 1003557<https://atlas.ripe.net/frames/probes/1003557/> 1003558<https://atlas.ripe.net/frames/probes/1003558/> 1003559<https://atlas.ripe.net/frames/probes/1003559/> 1003560<https://atlas.ripe.net/frames/probes/1003560/> 1003561<https://atlas.ripe.net/frames/probes/1003561/> 1003562<https://atlas.ripe.net/frames/probes/1003562/> 1003563<https://atlas.ripe.net/frames/probes/1003563/> 1003564<https://atlas.ripe.net/frames/probes/1003564/> 1003565<https://atlas.ripe.net/frames/probes/1003565/> 1003566<https://atlas.ripe.net/frames/probes/1003566/> 1003567<https://atlas.ripe.net/frames/probes/1003567/> 1003568<https://atlas.ripe.net/frames/probes/1003568/> Regards, Grzegorz Ponikierski

13 19

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