September 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

RIPE Atlas SMTP Measurement
by ripe.net＠toppas.net 11 Nov '22

11 Nov '22

Hello, i'd like to start a discussion about having a RIPE Atlas SMTP measurements. First of all: yes, i know there's a big obstacle for such a measurement type. A lot of probes are deployed using enduser internet-connections like dsl, cable, etc. with dynamic/eyeball IP addresses. Those IP spaces are usually blocked by SMTP servers as approach to reduce spam mails. For Example: by using blocklists like Spamhaus PBL. So a proper SMTP measurement wouldn't work. BUT we could have an easy way for RIPE Atlas probe hosters to signalize, that their probe is eligible for SMTP measurements: Step 1: enable "Simple DNS Entry" Step 2: create a matching reverse DNS record for the probes IP address Everybody who is able so configure a reverse DNS record for his probes IP address, is most likely using a non-dynamic/non-home ip address space e.g. a datacenter or office network. If an ISP provides the option for his customers to configure a reverse DNS record, it's most likely a "business-customer" subnet which can be used to run mailservers. After Step 1+2 are done, the RIPE Atlas platform would easily be able to verify if forward-confirmed reverse DNS is successful, and if so, automatically enable that probe for SMTP measurements. Alternatively: probe hosters choose their own Forward-confirmed reverse DNS name and submit it on the RIPE Atlas website. Also: if we would have STMP measurements, forward-confirmed reverse DNS should be mandatory for anchors, or is it already? Why should we have SMTP measurements? Besides general reachability checks, we could also evaluate SMTP response codes. But the most important thing for me is this: the SMTP protocol is old. Very old. From a security point of view, it's absolutely outdated. Most security features have been added years after the initial RfC. Thus, those security features are optional. Mandatory SMTP encryption is not provided by the SMTP RfC. So both sides have to signalize, that they are capable of encryption using the STARTTLS command. An attacker (man-in-the-middle) can perform a downgrade attack by suppressing the STARTTLS command. So both sides are forced to fallback and communicate unencrypted. RIPE Atlas would be a really good tool to identify such attacks, by monitor/measure the (enhanced) status codes of a target. But there's more! I see a two-sided model here. Either use the RIPE Atlas SMTP measurements to monitor/measure your own mailserver by alot of other RIPE probes out there, OR probe hosters could run SMTP measurements originating from their own probe to find out, if their own IP address is currently blocked by other mailservers. What do you think? BR, Simon

5 26

V5 probes
by Ernst J. Oud 10 Nov '22

10 Nov '22

L.S. Is there a sneak preview of the V5 probes available somewhere? Regards, Ernst J. Oud

8 14

API error
by Ernst J. Oud 07 Oct '22

07 Oct '22

Hi, Since a short while (1 or 2 days) I get an authorization error when downloading the data from the built-in first and second hop to ping.ripe.net. Thus: https://atlas.ripe.net/api/v2/measurements/1/results/?probe_ids=1004467&sta… Gives: {"error":{"detail":"Authentication credentials were not provided.","status":403,"title":"Forbidden","code":104}} If I logon with my credentials via “My Atlas”, I get: {"error":{"detail":"You do not have permission to perform this action.","status":403,"title":"Forbidden","code":104}} All other tests let me download the data fine, logged in or not. Same happens to download first and second hop data of other public probes. Any clues? Regards, Ernst J. Oud

2 2

RIPE Atlas Quarterly Planning Q4 2022
by Robert Kisteleki 27 Sep '22

27 Sep '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 start shipping the v5 RIPE Atlas hardware probes to hosts, ambassadors and sponsors as well as continue working on other items proposed by the community. We hope that by providing these plans, we can better inform the community of the ongoing developments on RIPE Atlas and get feedback on 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

Change in Probe Archive API
by Johan ter Beest 26 Sep '22

26 Sep '22

Dear probe hosts, Since 2013 we are creating a daily snapshot of the probe API which is available at https://atlas.ripe.net/api/v2/probes/archive Until today, this snapshot included some probes which had never connected. Starting with the snapshot of today (26 / 09/ 2022) we will exclude all never connected probes from the archive as they do not provide any useful information. Previous snapshots will not be altered. In addition to this change, every known probe will now have a probestatus page at https://atlas.ripe.net/probes/<probe ID>/ where previously some of these probes would generate a 404. Let us know if you have any question or comment about this change. Kind regards, Johan ter Beest RIPE Atlas Team

1 0

Riple Atlas + openwrt + docker + gns3 + debian
by Gery Escalier 07 Sep '22

07 Sep '22

Hi, I'm doing tests with OpenWrt SNAPSHOT, r20377-ca5c695a45 on docker in a gns3 lab and on debian 11. At the moment it allows me to carry out tests and later it will allow me to work with old routers and other hardware that can run openwrt. root@OpenWrt:~# /etc/init.d/atlasSyntax: /etc/init.d/atlas [command] Available commands: start Start the service stop Stop the service restart Restart the service reload Reload configuration files (or restart if service does not implement reload) enable Enable service autostart disable Disable service autostart enabled Check if service is started on boot Check if service is running status Service status trace Start with syscall trace info Dump procd service info get_key print probe public key (used for probe registration) probeid print probe id log print probe status log create_backup backup ssh key to tar.gz load_backup 'backup.tar.gz' load backup ssh key from tar.gz create_key create probe priv/pub key root@OpenWrt:~# /etc/init.d/atlas info{ "atlas": { "instances": { "instance1": { "running": true, "pid": 4707, "command": [ "/usr/libexec/atlas-probe-scripts/bin/ATLAS" ], "term_timeout": 5 I have done the configuration that the software probe account requires, I have done the configuration of the riple atlas package to generate the ssh keys and connect with my riple atlas account. I have had the probe 100% operational for several hours and generated credits, the problem I currently have is that when I turn off and start gns3 I have to install the Ripe Atlas packages from scratch in openwrt, configure it and generate the ssh keys again, update the keys in my Ripe Atlas account. At the moment I am using this option for testing, but it would be interesting if openwrt saves the data persistently, I am looking for information on what the problem may be, I am commenting on it in case someone who has used openwrt and something similar has come up. I will be updating news. Greetings. Gery

2 2

Group in Spanish Riple Atlas?
by Gery Escalier 06 Sep '22

06 Sep '22

Hello everyone, I have the doubt if there is any group in Spanish where I can participate, I have been documenting myself about Riple Atlas and I have been able to activate a software probe using openwrt, gns3 and Debian. It is always more interesting to be able to carry out tests and others participating with the community. I have seen some videos of the deployathons in which Michela G. and Agustin F. participated, that is why I was encouraged to configure the probe and understood a little better about the Riple Atlas project. I will also participate here and I will be sending emails with my queries. Thank you very much, best regards! Gery

4 6

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

02 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