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] Probes suffering DNS interception?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Kisteleki
robert at ripe.net
Tue Dec 15 14:19:35 CET 2020
On 2020-12-10 22:31, Edward Lewis 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 Hi, (Not replying to individual messages, but to the thread in general) Thank you all for the trigger, we re-vived this issue and will come up with a reasonable solution "soon" - hopefully measured in weeks, not years :-) In many cases the trigger "your probe is down" itself resulted host action, tough I do appreciate that an automated "it's fine now" can also help. Regards, Robert
- Previous message (by thread): [atlas] Probe operator notifications
- Next message (by thread): [atlas] Probes suffering DNS interception?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]