[atlas] Recovered probe v3

[Renny Leal]

Hi folks

I’ve recovered one V3 probe but sadly the person who got it flashed the tp-link 
original firmware to the device.

Is there any way to get the ripe atlas firmware back to it?

Thanks in advance


Enviado desde Correo para 
Windows

-- 
ripe-atlas mailing list
ripe-atlas@ripe.net
https://lists.ripe.net/mailman/listinfo/ripe-atlas

Re: [atlas] Proposal: Remove support for non-public measurements [ONLY-PUBLIC] (Robert Kisteleki)

[Renny Leal]

May the non-public measurements cost more in terms of credits or even money to 
support the infrastructure?

El 16 dic. 2022 11:28 a. m., ripe-atlas-requ...@ripe.net escribió:
Send ripe-atlas mailing list submissions to
ripe-atlas@ripe.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.ripe.net/mailman/listinfo/ripe-atlas
or, via email, send a message with subject or body 'help' to
ripe-atlas-requ...@ripe.net

You can reach the person managing the list at
ripe-atlas-ow...@ripe.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ripe-atlas digest..."


Today's Topics:

   1. Re:  Proposal: Remove support for non-public measurements
  [ONLY-PUBLIC] (Petr ?pa?ek)
   2.  RIPE Atlas Quarterly Planning Q1 2023 (Robert Kisteleki)
   3. Re:  Proposal: Remove support for non-public measurements
  [ONLY-PUBLIC] (Robert Kisteleki)
   4. Re:  Proposal: Remove support for non-public measurements
  [ONLY-PUBLIC] (Magnus Sandberg)
   5. Re:  Proposal: Generic HTTP measurements [GENERIC-HTTP]
  (Hugo Salgado)
   6.  New RIPE Atlas stream release (Chris Amin)
   7. Re:  Proposal: Measure well-known CDNs,[CDN-HTTP]
  (Stephane Bortzmeyer)


--

Message: 1
Date: Fri, 16 Dec 2022 12:21:03 +0100
From: Petr ?pa?ek 
To: ripe-atlas@ripe.net
Subject: Re: [atlas] Proposal: Remove support for non-public
measurements [ONLY-PUBLIC]
Message-ID: <06d70394-ea13-9be7-486e-a9017a77b...@isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 15. 12. 22 19:41, Steve Gibbard wrote:
> I worry that that would have a ?chilling effect? on use of the service.

I hear your concerns, and have a proposal how to quantify this concern:

- First, amend the page to say that all the data are public. (Possibly
also switch the flag, but that can be a separate step.)

- Second, observe what has changed in the usage pattern.

- Third, evaluate.

That way we don't need to stay in limbo over hypothetical situations but
get real data.


Side note about usefulness of one-off measurement history:
I think it _might_ be is interesting for anyone doing study on any given
outage, or even study about optimization practices over time.

For example, the DNS community has service called DNSViz which does just
one-off measurements, and yet, researchers come and write papers based
on data from DNSViz.

HTH.

--
Petr ?pa?ek



--

Message: 2
Date: Fri, 16 Dec 2022 12:32:11 +0100
From: Robert Kisteleki 
To: "ripe-atlas@ripe.net" 
Subject: [atlas] RIPE Atlas Quarterly Planning Q1 2023
Message-ID: 
Content-Type: text/plain; charset=UTF-8; format=flowed

Dear colleagues,

The quarterly plans for RIPE Atlas can now be found at:
https://www.ripe.net/support/documentation/quarterly-planning/ripe-atlas

In the last quarter, we worked on several proposals to change the RIPE
Atlas behaviour, including implementing general availability of HTTP
measurements and removing the ability to schedule ?non-public?
measurements.

This quarter, we?ll continue with the distribution of the v5 RIPE Atlas
hardware probes to hosts, ambassadors and sponsors as well as work on
other items proposed by the community.

If you have any input on our plans or want to let us know what you would
like to see us work on, please let us know.

Kind regards,

Robert Kisteleki
Research and Development Manager
RIPE NCC



--

Message: 3
Date: Fri, 16 Dec 2022 12:56:45 +0100
From: Robert Kisteleki 
To: Magnus Sandberg , ripe-atlas@ripe.net
Subject: Re: [atlas] Proposal: Remove support for non-public
measurements [ONLY-PUBLIC]
Message-ID: <36a79d58-83e1-4e93-a707-aa47a653a...@ripe.net>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi,

> The definition of a "small" test could be something like;
> - maximum 20 probes
> - runs for maximum 60 minutes
> - is repeated maximum 10 times
>  ? (if you run every 300sec you have to limit the endtime to 50 minutes)

What would you propose the API to do if this rule is violated? Should it
outright refuse the measurement, or should it silently turn on the
public flag (silently, because even if we emit a warning, it is probably
never seen by a human...)?

> With such limits you can troubleshoot things (non-publicly) but you
> can't build your monitoring system on top of that.

I guess this hinges on what level of support (legal, technical or other)
we're aiming for when it comes to others building services on top of
RIPE Atlas.

Regards,
Robert




--

Message: 4
Date: Fri, 16 Dec 2022 14:13:47 +0100
From: Magnus Sandberg 
To: Robert Kisteleki , ripe-atlas@ripe.net
Subject: Re: [atlas] Proposal: Remove support for non-public
measurements [ONLY-PUBLIC]
Message-ID: <2ed5e29a-9590-f20c-fd6f-f21e58846...@fallback.netnod.se>
Content-Type: text/plain; charset=UTF-8; format=flow