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] 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 ]
Romain Fontugne
romain at iij.ad.jp
Mon Dec 14 01:57:48 CET 2020
Another way is to setup a script listening at measurement id 7000. This logs all the probes connection/disconnection to RIPE controllers. Romain On 12/13/20 6:14 AM, Colin Johnston wrote: > +one from me, asked that this functionality be added 5 years ago. > >> On 12 Dec 2020, at 09:55, Gert Doering <gert at space.net> wrote: >> >> Hi, >> >> On Sat, Dec 12, 2020 at 09:03:54AM +0100, ripe at brite.cz wrote: >>> For this purpose I use an online ping check service. >>> Your probe need to have IPv6 or public IPv4 and ICMP be not blocked by a firewall to be able to respond pings from outside. >> >> This is not the point. Of course I could use our monitoring for that. >> >> The thing is "the system sends a DOWN report, but no UP report", and having >> to resort to external monitoring (which will not work for probes behind >> customer links with NAT) is quite lame. >> >> Gert Doering >> -- NetMaster >> -- >> have you enabled IPv6 on something today...? >> >> SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer >> Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann >> D-80807 Muenchen HRB: 136055 (AG Muenchen) >> Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > >
- Previous message (by thread): [atlas] Probe operator notifications
- Next message (by thread): [atlas] Probe operator notifications
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]