September 2024 - ripe-atlas - mailman.ripe.net

LACNIC42 IMWG call for presentation LAST DAYS!
by Elisa 19 Sep '24

19 Sep '24

Dear all, LACNIC 42 / LACNOG 2024 (7-11 October 2024, Asunción, Paraguay) is coming up and we will have a session for the Internet Measurements Working Group (IMWG)! We are looking for presentations on Internet measurements, network data collection, data analysis and tools. Please, submit your presentation proposal by sending an email to imwg-owner(a)listas.nog.lat We prefer talks of 15min. Include in your email: 1) a title; 2) a draft of the presentation; 3) a paragraph describing what you will talk about and why the topic is of interest for the community; 4) if you are planning to present in person or remotely. Thanks! Cheers, -- Elisa Peirano *Analista de Datos I+D* R&D Data Analyst /www.lacnic.net <http://www.lacnic.net> Latin American and Caribbean Internet Addresses Registry/

1 0

Not only are probes disconnecting…
by Ernst J. Oud 18 Sep '24

18 Sep '24

Current Atlas status shows a delay of over 16 hours. I created a measurement and no data is returned. It appears this is not a problem with only probes disconnecting… Ernst J. Oud

3 3

Auto reconnect?
by Ernst J. Oud 17 Sep '24

17 Sep '24

Is it true that probes will always automatically reconnect? Probe 60200 was down for a total f 17 hours (with a short reconnect of some minutes in the middle of that period). I just did a power recycle and it immediately reconnected. All my probes have reconnected now. Thanks for resolving this. Regards, Ernst J. Oud

1 0

Re: Again probe disconnects on ctr-dub-hw01 (Robert Kisteleki)
by ripe＠nurfuerspam.de 17 Sep '24

17 Sep '24

> they will > continue to run the defined measurements, reconnect when they can, and > send in all the stored results Actually, that seems not entirely true, at least not in all cases. That is how I mostly notice that one of my probes (likely) had a disconnect lasting more than a few minutes (but not enough to get a notification mail), because gaps in the RIPEstat graphs are noticeably visible as vertical gray bars without data points, or short gaps in an otherwise continuous line (at the typical graph resolution for a relevant measurement).

1 0

Again probe disconnects on ctr-dub-hw01
by Ernst J. Oud 17 Sep '24

17 Sep '24

Today my probes 60200 and 61071 experience several disconnects of upto an hour, both on controller ctr-dub-hw01. It appears this supposedly fixed disfunction has not been completely fixed. Regards, Ernst J. Oud

8 10

Subject-line in (dis)connect mails
by Marco Davids (Private) 11 Sep '24

11 Sep '24

Dear Atlas folks, I was wondering if it is possible to bring dis- and reconnect messages of RIPE Atlas probes more in line with each other. The disconnect mail has a subject like this: "Probe ID is disconnected (Name (ISP))" The reconnect mail has this: "Your RIPE Atlas Probe (ID: XXX) has reconnected" For me this is a bit confusing. When I sort my inbox alphabetically on subject, it would be really nice if the messages are grouped close together, which currently is not the case. It would helpful to me if this could be improved, by adjusting the specific text in the subject a bit. Thanks. -- Marco

5 10

probes do not register
by Randy Bush 10 Sep '24

10 Sep '24

on a SOHO LAN that used gto have a good running v3 probe (25867 but it went where so many v3 probes go, dead for a few months now. yes i did usb recovery, to no avail. you gotta love v3 probes.) i unpack an unused v3 (25909) i had in my back pocket for a few years. plug it into the LAN. wait a few hours. it does not register. power LED on, LED to right of it blinks about every two seconds. web page for it, https://atlas.ripe.net/probes/25909/ shows it has been down for 1 year 11 months while, in fact, it has never been up. oddly that web page shows the correct AS, comcast, 7922, but no IP addressing. tcpdump is my friend. pcap can be found at https://archive.psg.com/240907.atlas-25909.pcap it gets dhcp etc. then twice successfully pings to nl-ams-as3333-3.anchors.atlas.ripe.net (193.0.0.164) then it does successful DNS AAAA queries for woolsey.atlas.ripe.net and reg02.atlas.ripe.net. but it never reaches out to them that i can see. then it does a successful ARP for the default gateway, 192.168.0.1 then silence and much more silence unpack another unused antique from its envelope, 25918. dns queries for different controllers, but otherwise the same story. pcap avaliable as https://archive.psg.com/240907.atlas-25918.pcap. how to further debug? randy

3 5

RIPE Atlas Anchor Operating System Upgrade
by Paul de Weerd 02 Sep '24

02 Sep '24

Dear colleagues, RIPE Atlas anchors are scheduled for an Operating System (OS) upgrade soon since the current OS will reach its end-of-life on 30 June 2024 [1]. We are currently implementing and testing the necessary changes to support a smooth transition to the new OS without service interruption. Consequently, all live anchors will be upgraded by 31 August 2024. During this period, anchors will run on an outdated OS for a couple of months, but we do not anticipate any security issues here. For the few outward-facing services or lower-level software (such as the kernel) running on anchors, we will provide backports of necessary packages. If needed, we will shut down affected services or the anchor until the upgrade is complete. Due to this upgrade process, we have now paused applications for new anchors. New applications will resume from 15 July 2024 with anchors that will be provisioned with the new OS. If you have any questions please email gii-requests(a)ripe.net. Kind regards, Paul de Weerd RIPE NCC [1] https://www.redhat.com/en/topics/linux/centos-linux-eol

3 4