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/[email protected]/
[atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
- Previous message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
- Next message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Fri Aug 1 11:10:33 CEST 2014
> (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
- Previous message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
- Next message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]