June 2022 - ripe-atlas - mailman.ripe.net

Requesting Credits for Research
by Alex Gamero-Garrido 29 Jul '23

29 Jul '23

Hi folks, My name is Alexander Gamero-Garrido and I'm a 5th year PhD student at CAIDA, UC San Diego. We're soon launching a large traceroute campaign for research and could use your generous donation of credits. We'll need about 150 million credits, but any partial amount that gets us closer to that goal is welcome and greatly appreciated. My account is agamerog at eng.ucsd.edu Thank you, Alex -- *Alex Gamero-Garrido* *PhD Student, Computer Science* Web: cseweb.ucsd.edu/~agamerog Center for Applied Internet Data Analysis (CAIDA) San Diego Supercomputer Center UC San Diego Pronouns: He/Him/His <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> I'm using Inbox When Ready <https://inboxwhenready.org/?utm_campaign=signature&utm_medium=email&utm_sou…> to protect my focus.

13 15

Probe DHCPv6 support
by Aleksi Pirttimaa 19 May '23

19 May '23

Hi! I recently received my v4 probe and I'm very happy with it. But unfortunately it doesn't support DHCPv6. I present a practical reason for implementing a DHCPv6 client on the probe. You see, my ISP doesn't send router advertisements with the prefix for stateless autoconfiguration set, and instead DHCPv6 must be used. I believe their decision could have something to do with the fact that the regulating body here requires ISP's to prevent IP address spoofing in consumer plans. And to meet that requirement my ISP may be using a feature similar to Cisco's IP source guard, where switch ports and/or mac addresses are passively associated to leased ip's or prefixes, breaking SLAAC. Unfortunately they hate letting consumers talk with their engineers so it's difficult to speculate this further. For now, I've put a stateful firewall appliance in front of the probe which provides SLAAC, it works just fine. Do you think a DHCPv6 client should be implemented?

8 13

Probe on sailboat with Starlink
by Michael Markstaller 01 Sep '22

01 Sep '22

Hi, just a question: any interest to have a probe on a sailboat with Starlink (not officially supported) Just got my probe Probe #27837 fixed again at home (usb-stick RO/dead) and now I wonder if I leave it at home or take it with me over Adriatic/Atlantic. And if yes, some API-way to update location would be nice as we're moving:-) best regards Michael Markstaller Softwareentwicklung & IT-Dienstleistungen Am Birkengarten 19b 82024 Taufkirchen Tel: +49-89-21553825, Mobile: +49-179-2080789 USt-ID: DE293191950

11 14

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