- ripe-atlas - mailman.ripe.net

Shiny new v5 probe reveals problem with virtual probe
by Niall O'Reilly 01 Dec '22

01 Dec '22

Hello, everyone. TL; DR: clue needed configuring Turris Omnia for virtual Atlas probe. I'm delighted to have a shiny new v5 probe, which is operation since the day before yesterday. The new probe has been automatically tagged "IPv6 Works". On account of this, I've noticed that my virtual probe, running on my Turris Omnia, has the complementary tag, "IPv6 Doesn't Work." I suspect that I've not configured firewalling on my Turris properly. If any of you have sorted this, I would appreciate some clue. Thanks in anticipation. Niall

2 2

New V5 Probe with IPv4 Discovery issues
by Nate Weibley 01 Dec '22

01 Dec '22

I received a shiny new V5 probe via post on Saturday and got it up and running yesterday on my dual-stack network. The probe in question is: https://atlas.ripe.net/probes/62490/ It has been operational for about 18 hours and quickly indicated that IPv6 connectivity was functional, but it has only momentarily indicated IPv4 connectivity was established. I can see IPv4 ICMP and UDP traffic originating from the probe passing through my opnsense router on the IPv4 WAN interface so I know IPv4 traffic is flowing. I also see the correct IPv4 DHCP lease info for my LAN on the probe's network status page. Probe address discovery does not show a valid IPv4 connection address or IP Echo Service listed, only the Local IP of my probe. I've tried power cycling the probe but it doesn't seem to impact this issue. Are there any other troubleshooting steps I should try?

2 5

Format change for index pages of RIS MRT data files and RIPE Atlas daily dataset dumps
by Robert Kisteleki 24 Nov '22

24 Nov '22

Dear RIS and RIPE Atlas users, On Wednesday, 30 November 2022 we are planning to migrate the web server at <https://data.ris.ripe.net/> as well as <https://data-store.ripe.net> from Apache httpd to nginx. This will affect how the file listings in HTML index pages are generated, including the following: * RIS MRT data files (updates and dumps) * RIPE Atlas daily dataset dumps If you rely on the format of these pages, you need to update your software. Before we do the upgrade, you could check the new format of the index pages at: https://test-data.ris.ripe.net/rrc00/ We would like to ask you to avoid relying on the specific format of the index.html files. If you are fetching BGP dump files, please use the REST API that is described at: https://ris.ripe.net/docs/40_Prototypes/15_per_rrc_dumps.html You might also consider using per-peer dump files instead: https://ris.ripe.net/docs/40_Prototypes/10_per_peer_dumps.html We want to encourage you to provide your feedback on the API, so that we could improve it and build a similar API for the update files. If you are fetching update files, please use direct URLs to files as described at: https://ris.ripe.net/docs/20_raw_data_mrt.html#name-and-location Kind regards, Oleg Muravskiy, Robert Kisteleki RIPE NCC

1 0

Magellan
by Ernst J. Oud 18 Nov '22

18 Nov '22

L.S. In the meantime I have found that there is a hardcoded 5 minute timeout for streams to end. However, after this timeout the message “Disconnected from stream” appears and the ripe-atlas process appears to “hang”, a ctrl-c appears to be the only option, python then interrupts within threading.py and client.py. What is it doing, what is it waiting for? Any solution? Regards, Ernst J. Oud

2 1

Magellan streaming and ctrl-c behavior
by Ernst J. Oud 15 Nov '22

15 Nov '22

Hi, If I use the older Docker container for the ripe atlas CLI tools (Magellan) (at https://hub.docker.com/r/anuragbhatia/ripe-atlas-tools) a newly created measurement streams its results and then Magellan exits and the container exits. Since the aforementioned image is old and displays results wrongly using erroneous Unicode conversion, which was solved in later Magellan versions, I created a new image using the latest Magellan code. Now all is well except that after results have been streamed, Magellan waits for ctrl-c. This is as per the Magellan docs of the stream command, but very annoying. I planned to automate things, sending a ctrl-c keystroke is not easy in this case. I don’t know whether the older Magellan code did not wait for ctrl-c or whether the creator of the older Docker image changed the code somewhere. It would be an idea to add an option to the the Magellan measure command whether to stop after streaming or to stop after a certain amount of results are in, like the “—limit” command for the stream command which unfortunately is not an option of the measurement command. I think the only option is to create a measurement with the —no-report option, get the measurement-ID from the URL and then use the report command, instead of streaming. Any ideas? Met vriendelijke groet / Regards, Ernst J. Oud

1 0

Can't register software probe
by roberto.lucignani＠caleidos.it 15 Nov '22

15 Nov '22

Hi all, I download the probe software image from: https://github.com/Jamesits/docker-ripe-atlas Changed the RSA key in /var/atlas-probe/etc generating a new one with: ssh-keygen -t rsa -b 4096 Trying to register the software probe at: https://atlas.ripe.net/apply/swprobe/ I get the following error: * The public key does not match our regular expression for this key type I tried generating other keys, but I always get the same error. Regards, Roberto -- 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.

2 1

IPv6 and the V5 probe
by Eric Kochen 14 Nov '22

14 Nov '22

Hi, My V5 is up and running. For some reason public IPv6 is not detected or not working, yet. I have a dual-stack connection and IPv6 is a DHCPv6 Prefix Delegation configuration. Does this work with the V5 probe? Anything I need to configure at the Atlas website maybe?

2 3

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

placing a probe into wireless networks (not terrestrial)
by Kurt Kayser 11 Nov '22

11 Nov '22

Dear Atlas-ml-followers, this a summary of a brief discussion I had with Michel Stam during RIPE85. We believe there might be a great value putting up a public Internet monitoring probe (vantage point) into low earth orbit satellite systems, such as Starlink. Monitoring from terrestrial end-points delivers high variances, due to frequent sat-changes. If we could put up an ATLAS-probe (be it SW - which is probably easier than HW) into a specific plane, we could add interesting tests and try to interpret the values depending on position over specific areas, atmospheric influences, solar influences as well as other effects that would change signal patterns. I would be offering support to try to establish such a probe and help to setup a project defition. Any thoughts or feedback to this idea? Best regards Kurt Kayser

3 3

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