[atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network

Probes can request some https URL, asking for commands(say every 5
minutes), and if there is need to reboot the probe appropriate command can
be replied to appropriate probe.
This does not need an open SSH, or port forwarding. Does not affect
security but accomplishes goal of rebooting probes remotely (either
individually or by groups of probes) or sending to probes other commands.

Regards.
/Alex


On Fri, Aug 1, 2014 at 1:10 PM, Robert Kisteleki <robert at ripe.net> wrote:

>
> > (The way the probes signal problems by issueing special DNS requests
> > could be documented, though :) ).
>
> One can argue if we can/should do better, but in the meantime, the "network
> information" tab of the probe status page has the following:
>
> "SOS History (Showing only the last 25)
>
> This probe probably last rebooted on 2014-xxx
>
> The probe sends a message using DNS queries every time it tries to
> reconnect
> to the system. Below you can find a list of the most recent messages. The
> "power-up time" column shows the approximate "powered-up time" of the probe
> at the time of sending the message. "
>
>
> Cheers,
> Robert
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ripe-atlas/attachments/20140801/e21e77da/attachment.html>