This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Anchor reprovision
- Previous message (by thread): [atlas] Anchor reprovision
- Next message (by thread): [atlas] Anchor reprovision
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrew Asciutto
andrew at as1003.net
Fri Dec 1 16:22:04 CET 2023
I accidentally said probe in my original post, this is actually an anchor. The anchor doesn't seem to have a public key that's visible to me and there isn't a way to update a key for an anchor on the settings page. Thanks, Andrew Asciutto Senior Network Engineer https://www.as1003.net <https://www.as1003.net> On Fri, Dec 1, 2023 at 1:32 AM <netravnen+ripelist at gmail.com> wrote: > > > On Fri, 1 Dec 2023 at 02:04, Andrew Asciutto <andrew at as1003.net> wrote: > > Back in September I noticed my Ripe Atlas software probe corrupted > itself after an unscheduled DC power outage. I reinstalled the Ripe Atlas > anchor software, and left all network settings the same as last time but it > doesn't look like it connected back up to RIPE. Any ideas? Anyone with a > similar experience? > > I assume you remembered to update the public ssh key in the ripe atlas > settings page for your probe after the sw reinstall? > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20231201/6a199016/attachment.html>
- Previous message (by thread): [atlas] Anchor reprovision
- Next message (by thread): [atlas] Anchor reprovision
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]