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@ripe.net wrote:
Send ripe-atlas mailing list submissions to ripe-atlas@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@ripe.net
You can reach the person managing the list at ripe-atlas-owner@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@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@ripe.net> To: "Ponikierski, Grzegorz" <gponikie@akamai.com>, RIPE Atlas <ripe-atlas@ripe.net> Subject: Re: [atlas] Overuse of software probes Message-ID: <7f053467-59c6-69e0-6a33-44a1b42efdd2@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-06... https://sg-pub.ripe.net/emile/probe-similarity/probe_similarity_ipv6-2022-06...
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-fina...
------------------------------
Message: 2 Date: Wed, 29 Jun 2022 14:46:26 +0200 From: Daniel Karrenberg <dfk@ripe.net> To: Stephen Strowes <s@sdstrowes.co.uk>, ripe-atlas@ripe.net Subject: Re: [atlas] Probe on sailboat with Starlink Message-ID: <2df11fd5-5385-ee11-e5fc-ded5839a6beb@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@toppas.net To: Gert Doering <gert@space.net> Cc: ripe-atlas@ripe.net Subject: Re: [atlas] Assigned AS vs. Advertising AS Message-ID: <9049c43c-8f51-8710-9061-6ce680a83eeb@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 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,
On 29.06.22 10:54, Gert Doering wrote: Hi, 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