Hi, On Mon, Dec 16, 2013 at 03:11:37PM +0100, Robert Kisteleki wrote:
Due to an issue with the latest firmware release, a subset of the v3 probes were listening to incoming connections on an open port that should not have been left open. As a secondary measure, however, access to this port required credentials only available to the RIPE Atlas probe developers. It therefore never presented open access to the probes. This port (SSH) is used for development purposes in our internal development environment.
... actually, it would be great to have some sort of local "tell me if you are fine?" port to connect to... One of my probes is being difficult (it has network, it connects to the NCC, but it claims to not have an USB stick - which requires an on-site visit) and the lack of basic local diagnostic besides "run tcpdump and see what is happening" has already caused me two on-site visits, and now a third one for "replace the USB stick" (and/or find a USB port with more power). Two of those trips could have been saved by being able to just connect to some sort of status port... Better diagnostics at the atlas dashboard would have helped me, too, but for cases like "I think I have network by my DNS isn't working" or "I think I have network but can't connect to my controllers" errors, local data might still be beneficial. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279