October 2024 - ripe-atlas - mailman.ripe.net

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