- ripe-atlas - mailman.ripe.net

Anomaly in NTP measurement data
by ripe＠nurfuerspam.de 03 Nov '24

03 Nov '24

Hi, In the data to date of an NTP measurement (#80845985), I find a single strange outlier with respect to the RTT value calculated: { "fw": 5090, "mver": "2.6.4", "lts": 281, "dst_name": "time2.cloud.tencent.com", "ttr": 0.413039, "dst_addr": "119.28.229.79", "src_addr": "45.11.104.146", "proto": "UDP", "af": 4, "li": "no", "version": 4, "mode": "server", "stratum": 2, "poll": 8, "precision": 1.19209E-7, "root-delay": 0.0000915527, "root-dispersion": 0.0249329, "ref-id": "647a24c4", "ref-ts": 3939345482.4404373, "result": [ { "origin-ts": 3939346062.989854, "receive-ts": 3939346062.999974, "transmit-ts": 3939346063.0000167, "final-ts": 3939346062.995442, "rtt": 4294967296.005545, "offset": -0.007347 } ], "msm_id": 80845985, "prb_id": 7030, "timestamp": 1730357262, "msm_name": "Ntp", "from": "45.11.104.146", "type": "ntp", "group_id": 80845985, "stored_timestamp": 1730357293 }, When I do the math by hand, the "rtt" value I get is 0.0055453, nicely matching the fractional part found in the measurement data. Does anyone have an explanation as to where the weird integer part might come from? Some overflow/underflow or other issue with decimal math on a binary machine? (I am not sufficiently versed in computer science to fully understand that topic, just that there are challenges in that area.) Thanks! Kind regards, R.

1 0

request for RIPE Atlas credits
by 权晓文 30 Oct '24

30 Oct '24

Hello! I'm a PhD student at Tsinghua University in China. I'm currently involved in a measurement research project, which undertakes large - scale measurements similar to Ping and Tracert by means of RIPE Atlas. As a new user, I have no credits for further progress. Therefore, I'm asking for help. I would be very grateful if someone could provide me with some RIPE Atlas credits. Thank you so much.

5 8

Fwd: RIPE Atlas Virtual Anchor Registration for DCS1 (sg-sin-as37989)
by Sanjeev Gupta 30 Oct '24

30 Oct '24

Good morning, https://atlas.ripe.net/probes/7247 I had setup an anchor last year, on a VM. I realised today while cleaning up my Atlas account, that the anchor was shown as "Down". From what I can figure out, the VM was unregistered/deleted 6 months ago. Should I apply for a new Anchor, or can I re-install and re-register (I assume the ISO will be Atlas-specific). Regards -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Thu, 27 Jul 2023 at 22:22 Subject: RIPE Atlas Virtual Anchor Registration for DCS1 (sg-sin-as37989) To: Sanjeev Gupta <ghane0(a)gmail.com> Dear Sanjeev Gupta, Thank you for registering the technical information for your RIPE Atlas virtual anchor! Your FQDN is: sg-sin-as37989.anchors.atlas.ripe.net You will need now to setup the Virtual Machine according to these instructions: (https://atlas.ripe.net/docs/anchor-installation-vm/). It is important that once you have setup the virtual machine, you log in to your RIPE Atlas account, go to the "My Atlas" menu and then "Anchors", and check the boxes “Software is installed” and "Anchor is connected to the network" so we are notified and can begin the tests. Please note that your anchor will not be fully activated until we have finished these internal tests. We will notify you once we have finished testing and your virtual anchor is ready to use. If you have any questions, please do not hesitate to contact us at atlas(a)ripe.net You registered the following details: IPv4 address: 203.123.48.20 IPv4 ASN: 37989 IPv6 address: 2405:fc00::20 IPv6 ASN: 37989 Kind regards, RIPE Atlas Team

1 0

The MAT session is about to start
by Massimo Candela 29 Oct '24

29 Oct '24

A reminder that the Measurement, Analysis and Tools (MAT) session of RIPE89 is about to start in the main room at RIPE89! Streaming: https://ripe89.ripe.net/live/main/ Agenda: https://ripe89.ripe.net/programme/meeting-plan/mat-wg/ Ciao, Massimo On 17/10/2024 23:48, Massimo Candela wrote: > Dear all, > > > The MAT working group session will take place on Tuesday 29 October at > 16:00 CET. > > This is the agenda: > > 16:00 - 16:05 - Welcome - Chairs > 16:05 - 16:20 - Measuring and Visualizing DNS Watersheds - Jim Cowie > 16:20 - 16:30 - A First Look at User-Installed Residential Proxies From > a Network Operator's Perspective - Etienne Khan > 16:30 - 16:45 - IoT bricks over v6 - Tianrui Hu > 16:45 - 17:00 - Target Acquired? Evaluating Target Generation Algorithms > for IPv6 - Lion Steger > 17:00 - 17:15 - What’s in the Dataset? Unboxing the APNIC User > Populations - Vasilis Giotsas > 17:15 - 17:25 - RPKI flutter - Emile Aben > 17:25 - 17:30 - Closing Remarks - Chairs > > > If you are not already registered: https://ripe89.ripe.net/attend/register/ > > See you in Prague! > > Ciao, > Massimo (for the MAT WG chairs) > ----- > To unsubscribe from this mailing list or change your subscription > options, please visit: https://mailman.ripe.net/mailman3/lists/mat- > wg.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account > with the email matching your subscription before you can change your > settings. More details at: https://www.ripe.net/membership/mail/ > mailman-3-migration/

1 0

Request for Atlas Credits
by Felix Hoffmann 29 Oct '24

29 Oct '24

Hello All, I am Felix, a Master student at the University of Potsdam (Hasso-Plattner-Institut). I am working on a measurement research project that requires longitudinal data to validate censorship (at least that is what I want to try). For that, I would like to perform measurements like Ping, DNS, and HTTP. As it's just the start of the project, I can not yet estimate how many credits I need. For the beginning, it would be great to get some and then go from there. Therefore, I am reaching out for help. I would appreciate it if some of you could offer me some RIPE Atlas credits. My account at RIPE NCC is on this email: felix.hoffmann(a)student.hpi.uni-potsdam.de Best, Felix Hoffmann

11 15

probes getting free "stress test" by postal system
by Sulev-Madis Silber 29 Oct '24

29 Oct '24

i think we need more fun here. actually it's serious too i received my v1/v2 in post in just envelope with corner open my v3 came from our vesna herself (by hands) now, v5, came in huge box with just paper sheet and probe in it. the one corner was smashed in. and poor device had been flapping around, naked, in that box, so, that introduction leaflet developed several holes in it from sharp corners of probe enclosure sure, it's free, hence maybe it's unfair but maybe they need more love. unsure who even packs them. i would guess there could be *some* padding available to stuff there? from yt comments on probe introduction video i learned that they sometimes are questionable quality too. mass produced cheap? mine survived all this abuse and i attributed the flimsily glued box to what i learned from elsewhere, that it's a budget stuff but unsure what to think...

1 0

Re: Request for Atlas Credits
by Ziad Attia 29 Oct '24

29 Oct '24

Hi Felix, 30 million credits have been sent. Best of luck with your project. Kindest regards Ziad On Oct 29, 2024 11:22, Felix Hoffmann <felix.hoffmann(a)student.hpi.uni-potsdam.de> wrote: Hello All, I am Felix, a Master student at the University of Potsdam (Hasso-Plattner-Institut). I am working on a measurement research project that requires longitudinal data to validate censorship (at least that is what I want to try). For that, I would like to perform measurements like Ping, DNS, and HTTP. As it's just the start of the project, I can not yet estimate how many credits I need. For the beginning, it would be great to get some and then go from there. Therefore, I am reaching out for help. I would appreciate it if some of you could offer me some RIPE Atlas credits. My account at RIPE NCC is on this email: felix.hoffmann(a)student.hpi.uni-potsdam.de<mailto:felix.hoffmann@student.hpi.uni-potsdam.de> Best, Felix Hoffmann

1 0

Re-activated SW probe: How to get rid of red banner?
by ripe＠nurfuerspam.de 27 Oct '24

27 Oct '24

Hi I successfully reactivated and reconnected my software probe #1005585 that I had officially written off a few weeks ago. Now, how do I get rid of the red banner at the top of the probe management page reading "Note: this probe is most likely not operational, and as such it has been written off [...]"? Thanks! Kind regards, R.

1 0

Recycling software
by Ernst J. Oud 24 Oct '24

24 Oct '24

Hi, I get emails for RIPE to reconnect or return my abandoned probes. However, how do I send these software probes back to them? Is there a bit bucket email address or something? LOL. Regards, Ernst

7 7

Wrong IPv6 detected for my probe
by Matteo Bonora 23 Oct '24

23 Oct '24

Hello everyone, maybe it's me that I have an unusual configuration, but I was wondering if any of you are experiencing the same behavior... For IPv6 I use in my local network an ULA prefix, to maintain an abstraction layer between my network and the IPv6 prefixes assigned by my ISPs. Each ULA address of any of my devices gets translated via NPTv6 by my router to a global address compatible with my ISP assigned prefix. My probe as well has an ULA address and a public/global address that gets correctly detected by Atlas servers via IP Echo Service, but is the wrong IP that gets elected as the reference address within the Probe Address Discovery section. The correct one should come from IP Echo Service, but the ULA seems to be the preferred one. [image: 2024-10-23_00h07_14.png] Any ideas? Is there a way to force the selection of the IP Echo one? Thanks Matteo

3 2

Re: Changes to RIPE Atlas API keys
by Ponikierski, Grzegorz 22 Oct '24

22 Oct '24

Hi! > * We'll deprecate and remove the ability to use the URL form in about a > year (around October 2024). > * We plan to send further reminders about this change over time, as well > as reaching out to heavy users of the to-be-removed format. It’s October 2024. Is this plan still valid? I admit that I have a bunch of tools which use URL form which I would have to update to use "Authorization" header. Regards, Grzegorz From: Robert Kisteleki <robert(a)ripe.net> Organisation: RIPE NCC Date: Tuesday, 19 September 2023 at 12:11 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Changes to RIPE Atlas API keys Dear RIPE Atlas users, We'd like to update you on some upcoming changes regarding API keys in RIPE Atlas. TL;DR nothing changes regarding how you can use your API keys in the short term - as long as you're actually using them. However, we'll change how unused or forgotten keys are handled as well as remove the less secure in-URL use of them. At the moment RIPE Atlas users can query their existing API keys via the UI and API, including the possibility to retrieve old keys. In order to improve the security of how we handle these, we'll introduce the following changes in October 2023: * The listing (retrieval) of keys will only reveal parts of the keys (enough to identify them) in the API as well as in the UI. * We'll add the ability to "regenerate" an API key, which will replace the secret UUID of the key while keeping exactly the same permissions. * Unused API keys will automatically be frozen after 1 year of not being used. Active keys (i.e. the ones that have been used at least once) will not be frozen. You still have the ability to save your keys until these changes are done and, as written above, you will be able to regenerate them later. We'll notify this list when the changes are about to be done. In addition, in order to further increase the security of our system, in the long run we'll make changes about how these API keys are communicated to the API: * At the moment the API accepts these either in HTTP headers ("Authorization" header) or in the URL (?key=xyz), although the Authorization header version has been documented as the preferred version for some time. * We'll deprecate and remove the ability to use the URL form in about a year (around October 2024). * We plan to send further reminders about this change over time, as well as reaching out to heavy users of the to-be-removed format. Regards, Robert Kisteleki RIPE Atlas team -- ripe-atlas mailing list ripe-atlas(a)ripe.net<mailto:ripe-atlas@ripe.net> https://urldefense.com/v3/__https://lists.ripe.net/mailman/listinfo/ripe-at…<https://urldefense.com/v3/__https:/lists.ripe.net/mailman/listinfo/ripe-atl…>

2 3

webui dashboard is hard to use on mobile
by Sulev-Madis Silber 21 Oct '24

21 Oct '24

there has been some updates iirc but same issue remains got my busted v1/v2 -> v5 shipped and went to preconfigure it at dashboard, in phone, on android firefox, it's extremely hard to scroll dashboard without it dragging all the elements all over place it's also hard to open and close them, keep clicking 10 times around the open/close element and finally got it to react could maybe someone verify it, and fix maybe. perhaps lock it down somewhere? you must use some touch device for this as issue is in hold and drag really annoying each (rare) time i go there

3 2

HTTPS resource record.
by dikshie 18 Oct '24

18 Oct '24

Hi, Any plan to support HTTPS resource record in DNS measurement? example: ------------------- ;; ANSWER SECTION: www.ripe.net. 60 IN CNAME www.ripe.net.cdn.cloudflare.net. www.ripe.net.cdn.cloudflare.net. 300 IN HTTPS 1 . alpn="h3,h2" ipv4hint=104.18.4.245,104.18.5.245 ipv6hint=2606:4700::6812:4f5,2606:4700::6812:5f5 --------------------- Best Regards, -- -dikshie-

2 1

Probe #2413 somehow failing
by ripe＠brite.cz 14 Oct '24

14 Oct '24

Hi team, please have a look at Probe #2413, it shows connected but it seems it is not providing any measurements results. I tried different cables, power sources, connected to different switch, and finally move it to completely different location. It is v1 so it does not have USB memory stick. Please advise. Thanks Jiri

4 3

Re: Change git to repository (Randy Bush)
by ripe＠nurfuerspam.de 14 Oct '24

14 Oct '24

> and how does one "using the UI to replace the key?" On your probe's management page (e.g., https://atlas.ripe.net/ probes/1000006/), at the bottom of the page under the "General" tab, there is the option to add a new key. On a 5080 software probe, unless paths were changed during the build, one should find the public ssh key under /var/atlas-probe/etc/probe_key.pub (at least that's where it is on my Debian 12 system).

2 1

Change git to repository
by Jimmy Huybrechts 14 Oct '24

14 Oct '24

Hi, Currently my software probe on Debian 12 is using the git repository as there was no official deb when mine was deployed. Now I wish to change it out for the official repo, how can this be done? Or should I register the repository one as a new probe? -- Jimmy

4 6

Software Probe version 5100
by Michel Stam 07 Oct '24

07 Oct '24

Dear colleagues, We’d like to inform you that a new version of the software probe has been released, version 5100. Please find the changes below: All platforms As of this version, the ripe-atlas-probe-measurements repository on GitHub is deprecated. Its code has been merged into the ripe-atlas-software-probe repository Package can now be built with arbitrary shell shebangs. Note that only OpenWRT ash and bash are officially supported Bug fixed where permissions are wrong when systemd is disabled (reported by César de Tassis Filho <ctassisf(a)gmail.com>) A new code signing key has been introduced. It only signs Debian packages currently, but will sign the RHEL packages in an upcoming release as well. The current RHEL key will then be deprecated. This release already supports code signed using the new key Software probes Streamlined deployment on RHEL CI/CD systemd unit ownership moved to probe and anchor packages Debian 11/12 x86_64 support added Support for OpenWRT software probes and the hardware probes v3, 4 and 5 will be added in a future release. If you run RHEL or Debian, we encourage you to upgrade to the latest version: https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/Linux-… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/RHEL8-… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/RHEL9-… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/Debian… https://github.com/RIPE-NCC/ripe-atlas-probe-doc/blob/master/manuals/Debian… Best regards, Michel Stam, RIPE Atlas development team

2 3

Some built-ins are not working anymore
by Ernst J. Oud 07 Oct '24

07 Oct '24

I guess due to the new controller infra, the built-ins measurements for: ctr-ewr01.atlas.ripe.net ctr-fnc01.atlas.ripe.net ctr-sin02.atlas.ripe.net are invalid now? They don’t produce data since October 1st it seems. Will the new controllers be included as built-ins? Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud

2 1

About the recent connection problems
by Robert Kisteleki 02 Oct '24

02 Oct '24

Dear colleagues, As many of you have noticed, we have been experiencing some technical issues with RIPE Atlas over the past few weeks. I would like to explain some of these in this email. Earlier this year, we began the process of migrating our infrastructure from our on-premise and co-located data centres to a cloud-based solution. Significant work has gone into rewriting code for multiple components and to renew the underlying infrastructure, to containerise and adapt it for the new cloud environment. In the process of this, we have encountered unforeseen bugs and bottlenecks. The RIPE Atlas team has been working to fix these issues as we find them. We are largely done with the migration of the controlling infrastructure so we hope to have a more stable system in the coming days. We are deploying new code and fixes fairly often to prevent these issues from arising, but it is possible that you might experience unexpected disconnects, but hopefully on a smaller scale than the past weeks. In the coming weeks, we will also begin the migration of the website (the user interface and the API). To clarify some questions that we heard on the list: - We will be looking for a solution to compensate credits for the missing connection times. - In the vast majority of cases, we don’t expect data loss when probes are not connected. The measurement results are delayed until the probes can reconnect and submit the results. - We apologise for the many connection and disconnection emails you might have received when your probe is disconnected. Please note that you can change your email notification preferences on your probe status page. I understand that many of you will want a more detailed explanation. We will be publishing an article on RIPE Labs, and we plan to present our work at the MAT Working Group session at RIPE 89. Regards, Robert Kisteleki RIPE NCC

1 1

Atlas UI update 2024-09-23
by Stephen Suess 23 Sep '24

23 Sep '24

Hello Atlas fans, We just released an update to the UI that includes: - NEW: Results ASNs visualisation in DNS measurement overview map - CHANGE: Anchor list improvements (status, search, sorting) - CHANGE: Ambassador Probe card now allows inline note editing In addition, we have some improvements to the new advanced search in the probes and measurements lists, and some other under the hood improvements. If you want to see the full list of what has changed, you can check the release notes here: https://atlas.ripe.net/docs/releases/website/2024-09-23.html As always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

1 0

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

account e-mail change?
by Fallon Albrecht 29 Aug '24

29 Aug '24

Hi there, Thank you for your feedback. For security reasons, it is unfortunately not possible to change your RIPE NCC Access e-mail address. More information on this topic is available at: https://www.ripe.net/publications/documentation/disclosures-and-reports/rip… However, you can do the following: - Create a new RIPE NCC Access account with the new email address https://access.ripe.net/registration - You will need to enable two-factor authentication (2FA) to activate the account. - Transfer Atlas credits to the new SSO account If you need help or have any questions about this procedure, please contact ncc(a)ripe.net. We are always striving to improve RIPE NCC Access and our current work plans are available at : https://www.ripe.net/publications/documentation/quarterly-planning/business… Kind regards, Fallon Albrecht Product Owner RIPE NCC

1 0

Re: Globalping
by Ernst J. Oud 27 Aug '24

27 Aug '24

Stephane, That is precisely why I became interested, for a quick ping or trace they have a CLI where one can do a quick measurement or via the API. With Atlas Magellan in a docker container this is also possible, it streams the results to the console but Globalping might be a good add on tool in the toolkit. Thanks for the input. Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud > On 27 Aug 2024, at 14:03, Stephane Bortzmeyer <bortzmeyer(a)nic.fr> wrote: > > On Tue, Aug 27, 2024 at 12:42:18PM +0200, > Ernst J. Oud <ernstoud(a)gmail.com> wrote > a message of 12 lines which said: > >> It might be “cursing in the church” as we say in NL, but does anyone >> here have experience with the Globalping monitoring tools? > > https://www.jsdelivr.com/globalping ? > > No real practical experience but it seems interesting. The API is > well documented and a shell script as simple as: > > curl -H "Content-Type: application/json" \ > --data-binary @- \ > https://api.globalping.io/v1/measurements \ > <<EOF > { > "limit": 10, > "locations": [], > "target": "ayla.bortzmeyer.org", > "type": "ping", > "measurementOptions": { > "packets": 3 > } > } > EOF > > is enough to launch a measurement. You can see the resulting JSON at > https://api.globalping.io/v1/measurements/bqXml2MiDAoawobv if you want > an idea.

2 1

account e-mail change?
by Sulev-Madis Silber 27 Aug '24

27 Aug '24

i noticed i can't change my account mail address. unsure why we have such limitation here. i have mail i used for 25 years, or literally more than half of my entire lifetime, and now i want to change it. reason being it's ispmail i had since dialup. and they sold it. now i still have access to it but service sucks, despite expensive. a very good reason to change it. yet ripe seems to have account mail is permanent policy for no reason at all. i expect this to change after more updates. there was huge ui update but this feature is not coming. why? most of things allow me to change mail. with only handful of services insisting it being for life. i don't know if next one is lifetime long but at least now it's my own domain. hoping to change it. or at least given reason why i can't

5 8

Globalping
by Ernst J. Oud 27 Aug '24

27 Aug '24

L.S. It might be “cursing in the church” as we say in NL, but does anyone here have experience with the Globalping monitoring tools? Not as comprehensive as Atlas and a lot less probes but at first glance it has some useful features. Your thoughts? Regards, Ernst J. Oud

3 2

Call for presentations for LACNIC's Internet Measurements Working Group (IMWG)
by Elisa 27 Aug '24

27 Aug '24

Hi all, Call for presentations is now open! Seeking presentations on Internet Measurements (including, but not limited to, Atlas). The Internet Measurements Working Group session will be held at the LACNIC42/LACNOG2024 meeting in Asunción, Paraguay, on October 11. Presentations can be remote or in-person. Submission deadline September 20. Instructions: https://listas.nog.lat/archives/list/imwg@listas.nog.lat/thread/VSNIWWLMXGI… Kind regards, -- 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

Update on RIPE Atlas Service Issues
by Robert Kisteleki 26 Aug '24

26 Aug '24

Dear colleagues, After the mails to this list over the weekend, we just wanted to confirm that we are aware of the issues some of you are having and we are working to resolve them. A service announcement has already been posted, as some of you have already pointed out. We would also like to note that probes will automatically try to re-connect to the RIPE Atlas infrastructure as long as they are operational. This is not something the host can control and so there is no action needed on your part. Currently, we are in the final stages of re-working the probe-controlling parts of the RIPE Atlas infrastructure, and while we’re careful to keep the machinery running, we expect to encounter some hiccups as we complete this work. During this period, there might be additional issues that arise which affect network performance or the connectivity of probes. We will try to keep this list updated, but note that you can always find the status of our services on status.ripe.net, and we encourage you to check if there are known issues. Regards, Robert Kisteleki RIPE NCC

1 0

Disconnected probes…
by Ernst J. Oud 26 Aug '24

26 Aug '24

All, Some of my disconnected probes have connected again, but probe 60200 has not. This is not a network issue since on that router a SW probe (1005072) now connects fine (it was disconnected earlier today) Would restarting probe 60200 help? It is in an inconvenient place but if restarting helps let me know. Regards, Ernst J. Oud

2 1

Probe v3 id #22785 - BADMD-APP
by Cassiano Aquino 26 Aug '24

26 Aug '24

Hi, I have a probe with id #22785 that completed 10 years online last July, but today in the morning it stopped working. I tried the common procedure, remove the USB, which was the same the probe came with, never had major issues with it, restart, wait 10 minutes, put the USB drive back again. Usually this solved any problems I had in the past, but not today, after trying 4 different USB drives, I'm seeing the same error message on the SOS log: BADMD-APP-5080-d41d8cd98f00b204e9800998ecf8427e Is there anything else I can do? Considering that after ten years, this probe is almost part of the family, is there any hope to recover? I have another TP-LINK TL-MR3020 that I bought and almost never used, is it possible somehow to install the firmware on it to have it replacing the current probe? Thanks in advance, and I do understand if there is nothing we can do, but probe #22785, you will be missed! Cheers, Cassiano Aquino - EI5HPB

3 3

Fwd: Your RIPE Atlas Probe (ID: 60200) has reconnected
by Ernst J. Oud 25 Aug '24

25 Aug '24

> We're just letting you know that your probe (#60200 ) has re-established its link to our network and we are again receiving data from it. Good! After over 3 days. Connected to controller ctr-nue17. Not to ctr-dub anymore. Ernst

2 1

v2 probe repair?
by Phillip Remaker 24 Aug '24

24 Aug '24

Hello! I have an 11+ year old v2 probe Seems to be in a reboot loop. Starts up, all LEDs go blank, and it repeats. Any diagnostics I can do? Any repairs? https://atlas.ripe.net/probes/4111/#tab-network

3 5

Probe v3, problems
by Phillip Remaker 24 Aug '24

24 Aug '24

I tried to replace by failing v2 probe with a v3 probe I had mailed to me from a closed site https://atlas.ripe.net/probes/16058/' The first led is on, second is off, and 3rd is slow-blink, which indicates a "network problem"? I tried a different power supply, replaced the network cable, tried other ports and even put in a new power supply, all with no change. The DHCP server does not see it. Any other suggestions?

1 1

Disconnected #27262
by Victor TALVAZ 24 Aug '24

24 Aug '24

Hi everyone, It seems that I've been totally disconnected for 2 hours, 8 minutes, is the controller ctrl-dub-hw01 alive ? Probe #27262. Thanks, Regards, *Victor TALVAZ*

3 2

Another probe disconnected
by Ernst J. Oud 23 Aug '24

23 Aug '24

Hi, And just now probe 1004467 also has been disconnected. What is going on? Regards, Ernst J. Oud

6 9

Re: Auto reconnect?
by Ernst J. Oud 23 Aug '24

23 Aug '24

Ok. Hope so. But it is weird that probes try to connect to a controller that clearly is not responding. I have six probes, 5 work fine, 1 is now disconnected for 34 hours. If it would connect to the controller it always used to connect to - ctr-nue14- all would be well but it appears it persists to connect to a non functioning controller, probably ctr-dub-hw01. Or something else is going awry in fail over between controllers perhaps? I know this is a free non-critical service but the lack of communication here wonders me a bit. Especially since the downtime is longer than ever before. Ernst > On 23 Aug 2024, at 17:56, Nick Hilliard (INEX) <nick(a)inex.ie> wrote: > > Ernst J. Oud wrote on 23/08/2024 16:54: >> Do we need to take actions to have disconnected probes reconnect “over the weekend”? Or is a reconnect in this case automatically? > probes automatically reconnect, as far as I'm aware. > > Nick

1 0

Auto reconnect?
by Ernst J. Oud 23 Aug '24

23 Aug '24

I asked before but this list appears to be not for support questions? Try again… Do we need to take actions to have disconnected probes reconnect “over the weekend”? Or is a reconnect in this case automatically? Regards, Ernst J. Oud

1 0

RIPE NCC Atlas probes are going offline: `controller INIT exit with error`
by Marek Küthe 22 Aug '24

22 Aug '24

Hello, I am running two RIPE NCC Atlas Probes [1] [2] and both went offline a few hours after each other and a `controller INIT exit with error` appears in the log [3]. What can I do about this? The controller also seems to be somehow not pingable [4]. I use Debian 12 with the self-compiled .deb package (version 5090) and use a slightly hardened systemd unit [5]. [1] https://atlas.ripe.net/probes/1008669/ [2] https://atlas.ripe.net/probes/1008711/ [3] https://paste.i2pd.xyz/?2c936299e0b7473f#G9caVaD8bxLiDvSmHF4HEsZAEjMrW7Gchv… / https://paste.burble.com/?cecb8def804b373d#GyNsT22QBmii4PGZFnRnVP6mLQC9vhsv… [4] https://i.ping.pe/o/L/img_oL3R8bjI.png [5] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5d… I would appreciate an answer! -- Marek Küthe m.k(a)mk16.de er/ihm he/him

3 2

Also probe 60200 is disconnected (4G-T-Mobile)
by Ernst J. Oud 22 Aug '24

22 Aug '24

Hi, Yesterday (SW) probe 1005072 disconnected and this morning (HW) probe 60200 disconnected. This also happened on July 18th with exactly these same two probes, then it apparently was a problem in the Atlas infra. Please advice. Regards, Ernst J. Oud Begin forwarded message: > From: RIPE Atlas <no-reply(a)ripe.net> > Date: 22 August 2024 at 08:30:02 CEST > To: ernstoud(a)euronet.nl > Subject: Probe 60200 is disconnected (4G-T-Mobile) > Reply-To: RIPE Atlas <no-reply(a)ripe.net> > > Dear Ernst J. Oud, > > Your probe 60200 has been disconnected from the RIPE Atlas infrastructure since 2024-08-22 05:52:00 UTC. > > You may be able to learn more about the possible cause from the "Status" tab on your probe's information page: > > https://atlas.ripe.net/probes/60200/#!tab-status > > Probes are tagged with suspected problems every four hours, so if there is nothing listed under the Status tab and your probe has just gone offline, please check back in a few hours, as more information may be available. > > If you need further assistance or have any questions, please contact us at atlas(a)ripe.net. > > Kind regards, > > RIPE Atlas Team > > ********** > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/60200/, and click the "edit" button under "Notifications".

1 0

RIPE NCC Atlas probes are going offline: `controller INIT exit with error`
by Marek Küthe 21 Aug '24

21 Aug '24

Hello, I am running two RIPE NCC Atlas Probes [1] [2] and both went offline a few hours after each other and a `controller INIT exit with error` appears in the log. What can I do about this? The controller also seems to be somehow not pingable [3]. I use Debian 12 with the self-compiled .deb package (version 5090) and use a slightly hardened systemd unit [4]. [1] https://atlas.ripe.net/probes/1008669/ [2] https://atlas.ripe.net/probes/1008711/ [3] https://i.ping.pe/o/L/img_oL3R8bjI.png [4] https://codeberg.org/mark22k/dn42-router/src/commit/5c855adbbca45263268ba5d… I would appreciate an answer! -- Marek Küthe m.k(a)mk16.de er/ihm he/him

1 0

software probe DNS resolving not via OS functions
by Marco Moock 21 Aug '24

21 Aug '24

Hello! I have a software probe and it does many DNS requests. I installed the nscd cache on my machine, but the probe itself doesn't use the operating system's libc functions to resolve names. Is there a special reason for that? I am aware I can install a real local caching DNS server on the machine like dnsmasq, but I would like to ask the question. :-) -- kind regards Marco

2 1

Some RIPE Atlas calls take a long time
by Ben Cartwright-Cox 20 Aug '24

20 Aug '24

Hey folks, Anyone else getting issues with some RIPE Atlas API calls taking a very long time for calls that seem like they should be simple, like a credit check? # time curl https://atlas.ripe.net/api/v2/credits/ -H 'Authorization: Key xxx-xxxx' -o /dev/null real 0m6.394s user 0m0.063s sys 0m0.005s

2 1

RIPE Atlas Infra IP Rages
by Milad Afshari 20 Aug '24

20 Aug '24

Dear Atlas Team, I hope this message finds you well. Could you please provide the exact IP range(s) used by the RIPE Atlas infrastructure? This information is crucial for our ongoing network configuration. Thank you for your assistance. Best regards, Milad

6 7

Atlas UI update 2024-08-19
by Stephen Suess 19 Aug '24

19 Aug '24

Hello Atlas community, We have just released an update to the UI that includes (among other things): - NEW: Advanced search for probes and measurement listing pages - CHANGE: Header components with new icons to match ripe.net - CHANGE: Anchors cache updated on demand (instead of 24 hours) - CHANGE: Improved debounce, reduced error messaging on measurement form If you want to see the full list of what has changed, you can check the release notes here: https://atlas.ripe.net/docs/releases/website/2024-08-19.html As always, we hope you find these changes useful and we welcome your feedback. Kind regards, Stephen Atlas UI

1 0