- ripe-atlas - mailman.ripe.net

Proposal: remove per-hop “late” packets from traceroute [LATE-PACKETS]
by Robert Kisteleki 15 Dec '22

15 Dec '22

Dear RIPE Atlas users, We recently published a RIPE Labs article containing a few proposals: https://labs.ripe.net/author/kistel/five-proposals-for-a-better-ripe-atlas/. We'd like to encourage you to express your comments about this proposal (if you'd like to share them) here. Regards, Robert Kisteleki For the RIPE Atlas team

2 1

Atlas api down
by Ernst J. Oud 14 Dec '22

14 Dec '22

Hi, As of around 17:30 UTC on December 13th, all measurements other than built-ins, from the website or via Magellan, report no results. The website just hangs and Magellan times out. I believe all access via the api to be broken. I read that maintenance is pending, but that is scheduled the 14th… What’s up? Regards, Ernst J. Oud

3 6

atlas related mails come 4 times
by Endre Szabo 12 Dec '22

12 Dec '22

Hi chaps, Just recently any mail from atlas monitoring shows up 4 times in my inbox. 4 exact copies of a mail (Message-Id is also the same), in the same time, in 4 different SMTP sessions. Anyone else noticed such behavior? Also, I've just subscribed to this list and the subscription confirmation request mail came twice :D One via IPv4 and one via IPv6. Apparently no other senders have this issue on my end. --Endre

3 2

Unknown probe in my account
by Giuseppe Macario 08 Dec '22

08 Dec '22

Hello everyone, I have a probe that works properly but, a few weeks ago, my account also started to show a probe that doesn't work and that I don't know. I contacted atlas @ripe.net to ask for clarification but I didn't get anything (apart from a semi-automated message). So could anyone delete this unknown probe? https://atlas.ripe.net/probes/63078/ Thank you.

2 4

Removing the "technical updates" RSS feed
by Robert Kisteleki 07 Dec '22

07 Dec '22

Dear all, As of yesterday there's a new section in the documentation where we will publish information about the new releases for probe firmware and important UI/API changes: https://atlas.ripe.net/docs/releases/ With this, we plan to stop producing the RSS feed about "technical updates" - which had the same information until now. There's some use of this still, presumably from RSS readers that have been configured some time ago and fetch the feed ever since. (The top 5 clients accessing this correspond to 70% of the queries to this URL.) In theory we could retrofit the creation of the RSS feed into the new way of publishing the release news, but we would only consider this if there's a strong enough demand for it. So please let us know if you have reasons to insist on keeping the feed alive! Thank you, Robert Kisteleki RIPE Atlas

1 0

Issue to create measurement on the webpage
by Alexis MARCOU 07 Dec '22

07 Dec '22

Hi All, I'm trying to create a measure on the website : https://atlas.ripe.net/measurements/form/ But, when I click on the "Ping", a query is sent, but the interface is not updated with the parameters received ... Am I the only one with this issue ? Alexis

2 1

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