- ripe-atlas - mailman.ripe.net

Feature idea: new status "Probe (temporarily) closed for new UDMs"
by ripe＠nurfuerspam.de 20 Nov '24

20 Nov '24

Hi, Obviously, measurements are the purpose of being of the RIPE Atlas system. Thus, e.g., I take greate care to maximize probe uptime so measurements scheduled on them don't get disrupted by local events that are likely not representative of what most measurements are looking at. However, sometimes, temporary disruption may be known to come up, but is unavoidable, e.g., for maintenance of, or around the probe. Or a probe needs to be taken out of service "for good". In those cases, it is obviously hardly possible to avoid long-running measurements from being impacted, either by a short-term disruption, or by the removal of a probe altogether. And measurement owners obviously are aware of that, and need to take that into account in a way specific to each measurement's purpose. And it is obviously possible to remove, e.g., defunct probes from a running measurement and replace them with new ones. However, when a probe host knows _ahead of time_ that their probe will experience some event potentially disrupting measurements (like during planned maintenance activities), or will have to be decommissioned at a specific time in the future, how about if they could signal that condition to the Atlas infrastructure, and the infrastructure would at least not schedule _new_ measurements on such probes? E.g., by having a new probe "status" that can be explicitly set by the probe host to say, "this probe shall (perhaps just temporarily) not get any _new_ UDMs scheduled at this time (while the status is set)". Just a thought, not sure how much effort that would be to implement, and whether that would be worth the benefit of disrupting "fewer" measurements in case of foreseeable issues with a probe (or anchor), especially also upon an upcoming need to decommission one entirely. Thanks! Kind regards, R.

1 0

Re: [opensource-wg] RV: [ripe-list] Update on the Community Projects Fund 2024
by Rodolfo García Peñas (kix) 18 Nov '24

18 Nov '24

Hello, I would like to congratulate all the projects selected by the Community Projects Fund. I also wish to express my gratitude to the organising committee for initially selecting our project, 'RIPE Atlas distributed network telescope'. I am currently engaged in doctoral research on IBR traffic, and together with my supervisory team, we have proposed this project. We saw this as an ideal opportunity for the community to collect IBR traffic and make it available. We currently have a small working network of sensors (HoDiNT, Home Distributed Network Telescope [1]) and our objective is to extend the network and have RIPE manage the traffic collected. The HoDiNT sensors receive IBR traffic forwarded from the home connection router and forward it to a collector for analysis. They are fully compatible with Atlas sensors. This would enrich the traffic of other research centres, such as CAIDA or Merrit, and offer other students and research centres the possibility of having IBR traffic available for analysis. I was delighted that our project was selected, but a few hours later the organisation sent us an email stating that the RIPE Atlas team had raised some concerns about our proposal which may impact our ability to receive funding. We were requested to attend a meeting with the organisation and the RIPE Atlas team to discuss the proposal a few days later. The meeting was unfortunately not attended by a representative of RIPE Atlas. We were informed that the project was not deemed feasible. I would like to thank Alastair, who had to pass on the news to us, which is not an easy situation. I accept the decision taken, although I do not agree with either the substance or the form. I think we should have been given the opportunity to reformulate the project, maintaining the original objective but circumventing the limitations exposed. We will continue to improve HoDiNT in order to make it available to the community as soon as possible. If anyone is interested in contributing to the project, improving the code (mainly Python) and/or hosting sensors, please contact us. Due to limited resources, it is not possible to add sensors to the network openly, and we are doing so with sensors from colleagues and friends whom we thank for their time and resources. Regards, Rodolfo. [1] https://www.sciencedirect.com/science/article/pii/S138912862400402X [2] https://drive.google.com/file/d/1VGJ4PEcf-kHtFVT7rsXd9QYDqRL6rGH6/view?usp=… -- Rodolfo García Peñas (kix) http://www.kix.es/ "I asked him once how to change the key bindings and Dave said 'You use the Change Configuration command. On Unix it is abbreviated as cc.' Dave Conroy and Lawrence Stewart. On Friday, November 15th, 2024 at 14:18, Marcos Sanz via opensource-wg <opensource-wg(a)ripe.net> wrote: > FYI. Sorry for the cross-posting. > > > -----Mensaje original----- > > De: Alastair Strachan projectsfund(a)ripe.net > > Enviado el: jueves, 14 de noviembre de 2024 12:55 > > Para: ripe-list(a)ripe.net > > Asunto: [ripe-list] Update on the Community Projects Fund 2024 > > > > Dear all, > > > > After the announcement of this year’s Community Projects Fund recipients, > > some challenges emerged with the RIPE Atlas distributed network telescope > > project which would have prevented the project from achieving the goals > > outlined in the project plan. > > > > After careful consideration, the Selection Committee made the difficult > > decision to withdraw funding for the project. While we understand this is > > really disappointing for the recipients, we sincerely hope they will continue > > initiatives that bring value to our community and the Internet. > > > > The Selection Committee has now chosen another project to support from our > > pool of finalists: OpenPenny - An open-source tool to identify non-spoofed > > traffic. You can read about the project on the Community Projects Fund 2024 > > page: > > https://www.ripe.net/community/community-initiatives/cpf/previous- > > funding-recipients/funding-recipients-2024/ > > <https://www.ripe.net/community/community-initiatives/cpf/previous- > > funding-recipients/funding-recipients-2024/> > > > > Warm regards, > > Alastair Strachan > > Community Projects Fund Coordinator > > ----- > To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/opensource-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/

2 1

RIPE Atlas Community Project Update
by Michael J. Oghia 15 Nov '24

15 Nov '24

Hi all, See the message below from Alastair from NCC. Does anyone know if the project can re-apply for the next round of funding? Kind regards, -Michael ---------- Forwarded message --------- From: Alastair Strachan <projectsfund(a)ripe.net> Date: Fri, Nov 15, 2024 at 8:48 AM Subject: [ripe-list] Update on the Community Projects Fund 2024 To: <ripe-list(a)ripe.net> Dear all, After the announcement of this year’s Community Projects Fund recipients, some challenges emerged with the RIPE Atlas distributed network telescope project which would have prevented the project from achieving the goals outlined in the project plan. After careful consideration, the Selection Committee made the difficult decision to withdraw funding for the project. While we understand this is really disappointing for the recipients, we sincerely hope they will continue initiatives that bring value to our community and the Internet. The Selection Committee has now chosen another project to support from our pool of finalists: OpenPenny - An open-source tool to identify non-spoofed traffic. You can read about the project on the Community Projects Fund 2024 page: https://www.ripe.net/community/community-initiatives/cpf/previous-funding-r… Warm regards, Alastair Strachan Community Projects Fund Coordinator

2 2

Probe registration problem
by Robert Kisteleki 13 Nov '24

13 Nov '24

Hello, I just put up a status page entry to https://status.ripe.net/ as follows: We're experiencing a problem with accepting new and reconnecting probes in the infrastructure. Probe that are currently connected, as well as new and ongoing measurements and data delivery are not affected. Regards, Robert

1 1

Probe disconnected, will not register. Registration servers down?
by Ernst J. Oud 13 Nov '24

13 Nov '24

My software probe 1009171 disconnected yesterday, precisely when my WAN IP address changed. Since then it tries to register but fails. So I restored it from a backup with the same result. What it tries to do, over and over again already for 9 hours, is: —- /var/atlas-probe/status/reginit.vol does not exist try new reg Ping failed start reg ATLAS registration starting there is WAIT, REG_WAIT_UNTIL , now is 1731484426 REG_WAIT_UNTIL expired go re-reg 1731484366 now 1731484426 REGHOSTS reg03.atlas.ripe.net 193.0.19.246 2001:67c:2e8:11::c100:13f6 reg04.atlas.ripe.net 193.0.19.247 2001:67c:2e8:11::c100:13f7 ssh -p 443 atlas(a)reg04.atlas.ripe.net INIT reg server asked us to wait or there was an error. REG_WAIT_UNTIL 1731484557 condmv: not moving, destination '/var/atlas-probe/data/out/v6addr.txt' exists condmv: not moving, destination '/var/atlas-probe/data/out/simpleping' exists —- The address it uses for the ssh session to the registration server cycles between the 2 IPv4 and 2 IPv6 addresses shown on the REGHOSTS line above. Is this a problem on my end or are the registration servers down? Regards, Ernst J. Oud

4 4

probes getting free "stress test" by postal system
by Sulev-Madis Silber 13 Nov '24

13 Nov '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...

2 1

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

13 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.

2 1

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