On Mon, 13 Dec 2021 at 10:18, Johan ter Beest wrote:
> It is however in our plans to support an IPv6-only option.
>
> The biggest changes needed are in our monitoring, the installation
> process and our deploy as anchor process.
>
> Technically, AFAIK, there are no roadblocks anymore.
>
> We could
Hello,
On Thu, 8 Nov 2018 at 15:35, Alun Davies wrote:
> We just this morning published an article announcing that, as of today, we
> are accepting applications for anyone interested in hosting RIPE Atlas VM
> anchors. The article points you to all the information you’ll need to apply
> for an
On Sat, 17 Jul 2021 at 16:14, Milad Afshari wrote:
> I am curious to know if there is any way to remove a virtual RIPE Atlas probe
> from my panel?
See this earlier thread in the ripe forum. Should answer your question.
https://www.ripe.net/participate/mail/forum/ripe-atlas/PDgyMDdhZTQwLWZiZTYt
On Mon, 21 Jun 2021 at 08:20, Marco Davids (IETF) via ripe-atlas
wrote:
> Whenever my network get's a different IPv6-prefix from my provider
> (which happens every now and then), the probe is flagged down in the
> dashboard.
Does the delegated v6 prefix only change when your router power-cycles
On Sun, 20 Jun 2021 at 17:26, Peter Garner (iPad) wrote:
> Noob question. I set up my software probe on a Debian 10 box which has quite
> a few small servers on it. However, I intend to move it onto a Raspberry Pi,
> so I was wondering if there's a specific procedure to follow to preserve
> exi
On Sun, 21 Mar 2021 at 08:18, Lorenzo Colitti via ripe-atlas wrote:
> After more than 10 years (!) of 99% uptime (see below), my probe v1 appears
> to have given up the ghost. When connected to power, the lights still come
> on, but after a few seconds link bounces, and it never sends any packets
On Thu, 18 Feb 2021 at 12:06, Philip Homburg wrote:
> For a binary install of the CentOS RPM it should be automatic. For
> debian based, it is a matter of compiling a new .deb and upgrading
> (manually).
An idea for a system-tag in the RIPE Atlas system?
I.e. based on the (client) atlas probe sof
On Tue, 16 Feb 2021 at 17:40, Bengt Gördén wrote:
> I don't agree. This is a measurement tool. Whatever people think about
> extending
> or not extending the lifetime of ipv4 is irrelevant. It shouldn't hinder
> measurements of said networks. If there's networks out there that pass 0/8 and
> 240/
Hi RIPE Atlas,
Was reading through the documentation yesterday... Is there a specific
reason why it is NOT possible to update probe (ssh) pub keys via
authenticated API PUT/PATCH requests?
https://beta-docs.atlas.ripe.net/apis/metadata-reference/
--
Best regards,
Chriztoffer Hansen
Kyriacos,
On Mon, 8 Feb 2021 at 13:49, Kyriacos Sakkas wrote:
> It's not a big deal, more a mild irritation to have that probe listed. I
> mostly just get reminded about it once a month when the summary email comes.
If you are referring to the per-probe summary Email... Why not disable
this for
On Mon, 3 Aug 2020 at 12:14, Philip Homburg wrote:
> This is not an ideal place to discuss how atlas works. It would be better to
> use the atlas mailing list
> (https://lists.ripe.net/mailman/listinfo/ripe-atlas).
>
> In any case, we have 2 controllers for software probes. Those controllers are
On Wed, 17 Jun 2020 at 21:02, Thomas Schäfer wrote:
> is there a possibility to get notified if the probe has lost IPv6
connectivity?
+1
> At the moment it seems to me, notification only works if the connection
is down
> with both protocols.
... Inginious! 😻 (wonder if this question has been ask
On Sun, 16 Feb 2020 at 17:00, Jared Mauch wrote:
> Wondering if it makes sense to have a Debian and raspbian repo stood up for
> this. I could easily add this to my clusters of raspi to make the coverage
> broader.
Even if the RIPE NCC team only provided pre-compiled binaries as
downloadable fi
13 matches
Mail list logo
