- ripe-atlas - mailman.ripe.net

Fw: Action Required: RIPE Atlas Probe 52974 and RIPE NCC Days Sofia invitation
by Endre Szabo 20 Jun '23

20 Jun '23

Hi folks, I've got a probe running at a very remote site. Since the energy prices were skyrocketing with the crisis here in Eastern Europe, the probe does not have 7x24 power anymore. It is down for 10-ish hours a weekday. It's been running like this for months now. Suddenly, I've just got this mail below about my probe. The probe is online every day and was online today as well. Does this mail mean that RIPE is unsatisfied with my uptime, and I must return the probe? Or is it some monitoring needing some tuning? --Endre ----- Forwarded message from RIPE Atlas <no-reply(a)ripe.net> ----- From: RIPE Atlas <no-reply(a)ripe.net> Subject: Action Required: RIPE Atlas Probe 52974 and RIPE NCC Days Sofia invitation Date: Tue, 20 Jun 2023 13:01:05 -0000 Dear Endre Szabo, We hope this email finds you well. We noticed that your probe with ID 52974 has been disconnected for some time now, and you have probably received reminders from our system asking you to reconnect it. We would like to request you to please either reconnect the probe, or if that is not possible, to return it to us to be refurbished. There is a long waiting list of people keen to receive new probes, and because of global component shortages, we have a very limited number available. 1. You can check your probe using this link below. https://atlas.ripe.net/probes/52974/#tab-status If your probe is already online, you can stop reading here! 2. If you need to troubleshoot a disconnected probe, you can take a look at our tutorials on YouTube, or write to us asking for assistance. https://www.youtube.com/watch?v=BGj1MDIclDQ 3. If the probe is beyond repair, please go here: https://atlas.ripe.net/probes/52974 and click on the "Write-off" button at the bottom of the page. This will allow you to choose a reason for writing off the probe. This will clear the probe host name, and you will no longer receive any more reminders from us about the probe. 4. If you no longer wish to host the probe, please follow step 3 and then send the probe back to us. We will refurbish and redistribute it. Please use this address for shipping: RIPE NCC P.O. Box 10096 1001 EB Amsterdam The Netherlands ===== RIPE NCC Days Sofia, Bulgaria And finally, join us at RIPE NCC Days Sofia, Bulgaria on 27-28 June 2023! This free event provides a unique opportunity for network operators and technical staff to share knowledge and experiences. Don't miss out – register now at https://www.ripe.net/participate/meetings/regional-meetings/ripe-ncc-days-s… . We look forward to seeing you there! ===== Thank you for continuing to support RIPE Atlas. Best regards, The RIPE Atlas Team ----- End forwarded message -----

1 1

Can <contact@streamyard.com> please be unsubscribed?
by Carsten Schiefner 17 Jun '23

17 Jun '23

To whom it may concern… Thank you, -C.

3 2

Vergessen Sie nicht Ihre StreamYard-Einladung!
by StreamYard 17 Jun '23

17 Jun '23

StreamYard Inc. ( https://u7212249.ct.sendgrid.net/ls/click?upn=Ef-2BTvyZXeR9MIWcIdAYELFJPNYC… )

1 0

Sie wurden zu StreamYard eingeladen
by StreamYard 10 Jun '23

10 Jun '23

StreamYard Inc. ( https://u7212249.ct.sendgrid.net/ls/click?upn=Ef-2BTvyZXeR9MIWcIdAYELFJPNYC… )

1 0

upgrading an original soft probe
by Randy Bush 08 Jun '23

08 Jun '23

i have a probe, 1000004, on a deb 10 vm that was installed in the rotterdam hackathon. the detritus looks as if it was built using a deb install of atlasswprobe-5000-1.deb. two days ago, it stopped working in some way; i have not pursued, figuring i was dealing with an antique. is there a path to make it current? randy

4 9

Re: [atlas] credit request
by Michael Rabinovich 06 Jun '23

06 Jun '23

Many thanks! As I mentioned, I did get all the credits requested, but I am grateful to have them as it will allow us extra flexibility to do some exploratory measurements. Cheers, —Misha > On Jun 4, 2023, at 6:53 PM, DeuZa <proton(a)deuza.net> wrote: > > Sent 181 000 000 credits > > Sent from Proton Mail for iOS > > > Le mer. 24 mai 2023 à 17:29, Michael Rabinovich <michael.rabinovich(a)case.edu <mailto:Le mer. 24 mai 2023 %C3%A0 17:29, Michael Rabinovich <<a href=>> a écrit : >> >> Folks, >> >> As I posted couple months ago, we deployed and made available the instrumentation for longitudinal comparison of the performance implications of DNS resolver platforms, including ISP-provided and some influential publicly available resolvers ( https://dns-web-portal.netlify.app/). This work — and Nick Kernan’s MS thesis — was enabled by a generous donation of credits several years ago from the RIPE Atlas community — thanks a lot! Now to keep this measurement going requires ~20M credits per month. I’d like to assemble ~250M credits so we could keep this service up for a year. By then we should be able to see if it’s proved to be valued by the community and whether and how to keep it going beyond this time horizon. Would you please donate to my account what you can? >> >> Many thanks in advance! >> —Misha > <publicKey - proton(a)deuza.net - 0x714FB45F.asc>

1 0

credit request
by Michael Rabinovich 25 May '23

25 May '23

Folks, As I posted couple months ago, we deployed and made available the instrumentation for longitudinal comparison of the performance implications of DNS resolver platforms, including ISP-provided and some influential publicly available resolvers ( https://dns-web-portal.netlify.app/). This work — and Nick Kernan’s MS thesis — was enabled by a generous donation of credits several years ago from the RIPE Atlas community — thanks a lot! Now to keep this measurement going requires ~20M credits per month. I’d like to assemble ~250M credits so we could keep this service up for a year. By then we should be able to see if it’s proved to be valued by the community and whether and how to keep it going beyond this time horizon. Would you please donate to my account what you can? Many thanks in advance! —Misha

9 15

Probe DHCPv6 support
by Aleksi Pirttimaa 19 May '23

19 May '23

Hi! I recently received my v4 probe and I'm very happy with it. But unfortunately it doesn't support DHCPv6. I present a practical reason for implementing a DHCPv6 client on the probe. You see, my ISP doesn't send router advertisements with the prefix for stateless autoconfiguration set, and instead DHCPv6 must be used. I believe their decision could have something to do with the fact that the regulating body here requires ISP's to prevent IP address spoofing in consumer plans. And to meet that requirement my ISP may be using a feature similar to Cisco's IP source guard, where switch ports and/or mac addresses are passively associated to leased ip's or prefixes, breaking SLAAC. Unfortunately they hate letting consumers talk with their engineers so it's difficult to speculate this further. For now, I've put a stateful firewall appliance in front of the probe which provides SLAAC, it works just fine. Do you think a DHCPv6 client should be implemented?

8 13

Measurement suggestions for new deployments.
by Gerardo Huerta Robles 18 May '23

18 May '23

Hello all, I'm a newbie with RIPE ATLAS Probes, We are currently working on deploying a new Probe network in Nicaragua as the first step for a measurement project. The second step will be to capture statistics of traffic to the internet, but we are not clear what kind of targets are the most relevant for internet statistics. I would like to ask you for suggestions of targets, what kind of public servers are relevant for user internet traffic? We are thinking of DNS servers like 8.8.8.8 or some public HTTP web pages like the government or social media like Facebook, youtube and so on. But what do you think? Do you have some advice? The project is intended to obtain the first statistics about internet traffic and make it public using RIPE Probes and schedule measurements. If you have some advice please let me know, Thank you. Regards

1 0

RIPE Anchor updates?
by John Howard 16 May '23

16 May '23

Hi folks, Proton hosts 3 RIPE Anchors (7120, 6847, 6854) and during routine vulnerability scanning we identified these appliances running nginx 1.20.1, which is potentially vulnerable to two CVEs (CVE-2022-41741 and CVE-2022-41742). Given the mp4 module pre-req, I doubt they are vulnerable in practice, but this highlighted that the nginx 1.20 train was deprecated 11 months ago, and 1.23/1.24 are the currently active releases. I note the last probe firmware update 5080 (which we run already) from Nov/22 disabled auto updates on the appliances, so I assume there will be regular updates coming from RIPE going forward instead? Thanks John -- John Howard Head of Network Infrastructure Proton AG Sent with Proton Mail secure email.

2 3