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 ]
Colin Johnston
colinj at mx5.org.uk
Thu Dec 10 22:33:59 CET 2020
I said it would be useful for probe up messages five years ago Col > On 10 Dec 2020, at 21:31, Edward Lewis <edlewisjr at cox.net> wrote: > > (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 > > >
- Previous message (by thread): [atlas] Probe operator notifications
- Next message (by thread): [atlas] Probe operator notifications
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]