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] Probe operator notifications
- Previous message (by thread): [atlas] Probe operator notifications
- Next message (by thread): [atlas] Probe operator notifications
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ponikierski, Grzegorz
gponikie at akamai.com
Fri Dec 11 12:14:59 CET 2020
+1 for 'your probe came back on-line' Regards, Grzegorz From: Edward Lewis <edlewisjr at cox.net> Date: Thursday 2020-12-10 at 22:32 To: "ripe-atlas at ripe.net" <ripe-atlas at ripe.net> Cc: Ed Lewis <edlewisjr at cox.net> Subject: [atlas] Probe operator notifications (Seeing the thread about DNS intercepted probes reminded me to send this:) For 5 or so years running I have a probe operating in my garage (behind my home’s NAT and using the ISP’s NXDOMAIN rewriting, non-DNSSEC handling recursive server) a run-of-the-mill home cable set up. When I got my November report, it said I’d been down the last half of November. That was news to me. I then down'd/up’d it and it reconnected and seems to be on-line again. I do get the “your probe went off-line” notices. I would like “your probe came back on-line” notices as well. If we had those, I may have noticed it stayed down after the last message I saw. Ed -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-atlas/attachments/20201211/ca7612c6/attachment.html>
- Previous message (by thread): [atlas] Probe operator notifications
- Next message (by thread): [atlas] Probe operator notifications
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]