- ripe-atlas - mailman.ripe.net

Join the DNS Hackathon on 20 and 21 May in Rotterdam (weekend before RIPE 86)
by Vesna Manojlovic 22 Mar '23

22 Mar '23

Dear colleagues, I am pleased to invite you to participate in the DNS hackathon that will take place the weekend before RIPE 86 at Ahoy in Rotterdam, on Saturday 20 May and Sunday 21 May 2023. The hackathon is organised by DNS-OARC, Netnod and the RIPE NCC and offers projects based on three challenges: DNS &... Sustainability Security (and privacy) Sovereignty You can also bring your own idea or project. To participate, apply here: https://www.ripe.net/participate/forms/apply/dns-hackathon-2023/ (first deadline is on Thursday, 23 March 2023) Read more at: https://www.netnod.se/join-the-dns-hackathon-2023 Feel free to share this invitation with your communities. Regards, Vesna Manojlovic -- Senior Community Builder, RIPE NCC https://labs.ripe.net/author/becha/

1 0

HTTP measurement proposals [CDN-HTTP] [GENERIC-HTTP] [PEERING-HTTP]
by Ethan Katz-Bassett 06 Mar '23

06 Mar '23

Hi Robert, all: I was considering emailing about the possibility of HTTP measurements to our PEERING <https://peering.ee.columbia.edu/> testbed when I stumbled on the five proposals that Robert posted in December. I want to express my strong support for the two HTTP proposals. Hourly [CDN-HTTP] would be great (eventually with HTTPS support). ([STARTTLS] also sounds good, but I haven't thought deeply about it, and [ONLY-PUBLIC] sounds good unless it costs RIPE Atlas support / probe hosts) I was wondering about the feasibility of allowing HTTP measurements towards PEERING experiments (meaning, towards our address space announced from an experiment via our routers). Is that something that you might be open to supporting? This came to mind because we are in the process of onboarding PEERING to some bring-your-own-prefix services offered by CDNs and cloud providers, and so an increasing number of PEERING experiments are about content delivery/cloud hosting, and it would be great if RIPE Atlas could act as measurement clients to provide widespread vantage points. One hands-off option that comes to mind is to set them up similar to the proposal for CDN-HTTP, where probes will regularly fetch an object at a fixed URL, say http://ripeatlas.ee.columbia.edu/testobject. Normally, that could resolve to our project webserver, which is hosted in AWS. When an experiment needs this HTTP capability (all experiments undergo review by at least 2 people for safety, and we enable only the capabilities they request and need, following the principle of least privilege), we could instead redirect it to a PEERING address allocated to the project that would host the same test object but that would be announced from cloud/CDN/PEERING sites however the experiment had configured. Alternatively, it could be a measurement available to approved accounts, and we could pass on which experiments are approved, or perhaps available to all accounts. We have fixed address space, if you have a way to whitelist. We maintain our list of prefixes as RS-PEERING-TESTBED on RIPE's IRR. I believe Johan recently contacted Kevin Vermeulen about talking to us about RIPE Atlas in the context of another one of our projects, so possibly we can have a discussion covering both topics. Thanks for all your work providing the platform -- it's great! Ethan -- http://www.columbia.edu/~ebk2141/

1 0

Errors on Measurement web interface
by ripe＠brite.cz 01 Mar '23

01 Mar '23

Hi team, I see issues with Latencymon, such as https://atlas.ripe.net/measurements/48750273/#latencymon Upon opening it displays message "Server is responding slowly", after a while it displays the default view. But when I expand the time range a bit, or make any change to the view, it will show nothing and after a while displays message "It is not possible to download data from the API" Tried Firefox and Chrome, same result. The same result when I open only the frame, such as https://atlas.ripe.net/frames/measurements/48750273#latencymon

2 1

Re: [atlas] Measurement question
by Michel Stam 20 Feb '23

20 Feb '23

Hello Roberto, I’ve done the exact same measurement too, using the 3 types of traceroute available (ICMP, UDP and TCP). UDP: (https://atlas.ripe.net/measurements/49826077/#general) TCP: (https://atlas.ripe.net/measurements/49826078/#general) ICMP: (https://atlas.ripe.net/measurements/49826076/#general) The way the traceroute works in Atlas is that if 5 hops have been received without response, the trace skips over to TTL 255 and ends the traceroute. This is what you see with TCP and ICMP. The traceroute stops for lack of response. To prove that, I’ve run the trace again, skipping hops 1-7, for both ICMP and TCP: https://atlas.ripe.net/measurements/49826868/#general https://atlas.ripe.net/measurements/49826959/#general Now for the interesting bits: 100.64.0.0/10 is CGN (Carrier Grade NAT), RFC 6598. Looking at the traceroute differently: Hop 1 (AS16509, Amazon EU West, Amazon-02) Hop 2-7 CGN Hop 8-9 (AS unknown, but between UK and US, IPROU3-ARIN, so Amazon IP routing 3) Hop 10 (AS unknown, but between UK and US, IPROU3-ARIN/ARMP-ARIN, Amazon IP routing) Hop 11-15 CGN Hop 16 (AS unknown, presumably US, IPROU3-ARIN/ARMP-ARIN, I presume Amazon IP routing still) Hop 17-19 CGN Hop 20 (AS13335, Cloudflare US) So it seems like every cloud zone interconnect (amazon Europe west, US, then Cloudflare) transitted goes through a CGN setup. Not sure but I can understand if this confuses some types of traffic. I don’t think there’s anything wrong with your setup, but the results are interesting. I’ve copied a couple of our researchers onto the mail as they may be interested in this as well. Regards, Michel > On 8 Feb 2023, at 11:33, roberto.lucignani(a)caleidos.it wrote: > > Hi Michael, > for example, one measure ID is this one: 49813750 > The result says there are 7 HOPS. > The result of the traceroute made directly on the host is the following one > traceroute to www.madghigno.tech (172.67.221.209), 30 hops max, 60 byte packets > 1 52.56.0.19 24.303 ms 52.56.0.31 9.067 ms 52.56.0.17 29.663 ms > 2 * 100.65.18.192 7.843 ms 100.65.19.176 6.252 ms > 3 100.66.8.254 1.563 ms 100.66.8.146 0.697 ms 100.66.8.168 1.449 ms > 4 100.66.10.138 8.469 ms 100.66.10.14 5.713 ms 100.66.10.6 8.127 ms > 5 100.66.7.77 1.653 ms 100.66.6.173 2.658 ms * > 6 100.66.4.75 2.726 ms 100.66.4.87 2.327 ms 100.66.4.89 1.550 ms > 7 100.65.10.65 0.533 ms 100.65.11.1 0.857 ms 100.65.10.161 8.616 ms > 8 15.230.158.29 2.062 ms 15.230.158.171 5.998 ms 15.230.158.27 1.617 ms > 9 15.230.158.164 1.315 ms 52.94.33.120 2.089 ms 15.230.158.40 1.484 ms > 10 54.239.101.83 1.440 ms 150.222.65.23 1.358 ms 54.239.101.87 1.897 ms > 11 100.91.211.7 1.368 ms 100.91.13.66 1.956 ms 100.91.13.100 5.077 ms > 12 100.91.210.16 1.837 ms 100.100.6.119 1.848 ms 52.93.134.81 2.178 ms > 13 100.100.73.70 2.434 ms 100.91.203.106 4.546 ms 100.100.85.70 1.139 ms > 14 100.91.207.15 1.289 ms * 100.100.72.67 1.767 ms > 15 100.100.2.76 3.616 ms 100.91.201.140 1.955 ms 100.91.205.18 1.744 ms > 16 99.83.89.19 6.820 ms 100.91.201.1 2.454 ms 100.91.201.97 2.415 ms > 17 100.91.211.89 17.823 ms 172.71.176.2 3.200 ms 172.70.160.2 4.450 ms > 18 100.100.6.77 1.805 ms 100.100.6.3 1.943 ms 100.100.6.111 2.005 ms > 19 100.100.80.70 1.980 ms 100.100.76.134 2.679 ms 100.100.69.134 2.081 ms > 20 172.67.221.209 2.799 ms 100.100.89.209 7.318 ms 100.100.89.17 6.869 ms > Since the website is served by cloudflare the route may vary between requests but the are always around 18/20 HOPS > I don’t understand if I0m missing something here. Let me know if you need further details > Regards, > Roberto > From: Michel Stam <mstam(a)ripe.net> > Date: Wednesday, 8 February 2023 at 10:13 > To: roberto.lucignani(a)caleidos.it <roberto.lucignani(a)caleidos.it> > Subject: Re: [atlas] Measurement question > Hello Roberto, > Would you be able to share screenshots/measurement ids so we can have a look? > Regards, > Michel > > > On 8 Feb 2023, at 09:04, roberto.lucignani(a)caleidos.it wrote: > I’m doing some measurement from one of my software probes, the measure is a traceroute to a destination. > The results I get are completely different from what I see doing the same traceroute directly on host where the probe is installed. I configured the measure to sue the DNS resolution on the probe.. > From the Atlas portal I get a traceroute with 7 hops, doing it directly on the host returns 28 hops, for the same destination. > Why this difference ? > Regards, > Roberto > -- > Mail sent with Outlook for Mac > This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this message from your system. E-mail transmission cannot be guaranteed to be secure or error-free, because information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission. > -- > ripe-atlas mailing list > ripe-atlas(a)ripe.net > https://lists.ripe.net/mailman/listinfo/ripe-atlas

2 4

Offering a v1 probe for adoption in RU
by Roman Mamedov 20 Feb '23

20 Feb '23

Hello, I am offering my probe to someone else within Russia for "adoption" (ownership transfer). Despite being a v1, it still runs well with no downtime. Contact me on Telegram via @romanrm to discuss (in Russian or English), or via E-Mail if you don't have an account. Thanks -- With respect, Roman

1 0

Atlas V5 - Rack-Mounting Solution
by Johannes Schiemer 19 Feb '23

19 Feb '23

Dear all, As I have just received my Atlas V5 Probe and wanted to mount it in my Rack, I've decided to 3d-Print a holder for the probe. I've also decided to share it with all of you in the hopes that some of you might find it useful. This is the link to thingiverse: https://www.thingiverse.com/thing:5864347 Thanks! Greetings, Johannes

1 0

Missing ping and traceroute dumps for 2023-01-23
by Maxime Mouchet 15 Feb '23

15 Feb '23

Hi, I noticed that there is no ping and traceroute dumps for 2023-01-23: https://data-store.ripe.net/datasets/atlas-daily-dumps/2023-01-23/ The other days are fine though. Is there any chance to get these dumps? Or are they just lost? Thanks! Maxime

2 3

Measurement question
by roberto.lucignani＠caleidos.it 08 Feb '23

08 Feb '23

I’m doing some measurement from one of my software probes, the measure is a traceroute to a destination. The results I get are completely different from what I see doing the same traceroute directly on host where the probe is installed. I configured the measure to sue the DNS resolution on the probe.. >From the Atlas portal I get a traceroute with 7 hops, doing it directly on the host returns 28 hops, for the same destination. Why this difference ? Regards, Roberto -- Mail sent with Outlook for Mac This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this message by mistake and delete this message from your system. E-mail transmission cannot be guaranteed to be secure or error-free, because information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmission.

1 0

New ripe-atlas-tools and ripe-atlas-cousteau
by Chris Amin 07 Feb '23

07 Feb '23

Dear colleagues, I'm pleased to announce the release of version 3.1.0 of the RIPE Atlas command-line tools, which allow you to use RIPE Atlas from the comfort of your shell: https://github.com/RIPE-NCC/ripe-atlas-tools/ The changes for this release include: * Improved probe-search and measurement-search, including machine-readable "csv" and "tab" output formats * --stream-timeout and --stream-limit added to measure command In addition, this release depends on the new ripe-atlas-cousteau==2.0.0, which uses the new WebSocket-based RIPE Atlas streaming API. Regards, Chris Amin RIPE NCC

1 0

Rate limiting on the APIs
by Robert Kisteleki 06 Feb '23

06 Feb '23

Dear all, We have seen in the past that even with the best intentions, every now and then some users are using excessive amounts of requests to the RIPE Atlas APIs, in some cases resulting in degraded performance to all users. An example for the curious: some AWS account asking the probe API for live queries once a day at 8am like clockwork; over a million queries for probe statuses (note: we don't have a million probes - every query is repeated hundreds or thousands of times) [1] We will apply rate limiting to protect from (some of) these. In particular: * The API in general will impose a limit of no more than 300 queries/second (if done over multiple connections) * The measurement API in particular will impose a limit of 150 queries/second (if done over multiple connections) * When reaching the limit, an HTTP response code of 429 (Too Many Requests; https://www.rfc-editor.org/rfc/rfc6585#section-4) will be given. According to our logs these limits will in general not be visible to users. Users going over these limits will see the 429 response code; client libraries should be able to handle this. We will observe the effect of these measures to determine if we need to tighten further - or perhaps relax them. We plan to apply these changes sometime next week; I'll let you know once they are in place. Regards, Robert [1] a much better way of doing this is to use the probe archive (https://ftp.ripe.net/ripe/atlas/probes/archive/); this is one-time fetch of 2MB or so and probe statuses are pretty stable in general

1 1