- ripe-atlas - mailman.ripe.net

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

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

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