Hi, I receive a week ago our first probe but I'm unable to make it appear as online at the website. I can see it requests DHCP, it gets an IP address (NATed), it does some measurements (like HTTP and NTP) successufly but at atlas.ripe.net it is listed as 'Never online'. It rebooted around 3 times in the last week and each time was kept as least 24h in a row with no power down or cable disconnect. The MAC ADDRESS at the website matches with the MAC ADDRESS labeled in the probe. How should I proceed to get this fixed? Best regards, Thiago Ayub
Most of the time I see this happen with there is too little power applied to the USB power. How are you powering it? On Wed, Oct 7, 2015 at 6:28 PM, Thiago Ayub <thiago.ayub@upx.com.br> wrote:
Hi,
I receive a week ago our first probe but I'm unable to make it appear as online at the website. I can see it requests DHCP, it gets an IP address (NATed), it does some measurements (like HTTP and NTP) successufly but at atlas.ripe.net it is listed as 'Never online'. It rebooted around 3 times in the last week and each time was kept as least 24h in a row with no power down or cable disconnect.
The MAC ADDRESS at the website matches with the MAC ADDRESS labeled in the probe.
How should I proceed to get this fixed?
Best regards,
Thiago Ayub
Hi Thiago, If you're sure that the probe gets IP, can you also make sure that the probe can do tcp/443 to outside world and DNS is working? I do not see any connection attempts from your probe to our infrastructure. Cheers! /vty On 10/8/15 3:28 AM, Thiago Ayub wrote:
Hi,
I receive a week ago our first probe but I'm unable to make it appear as online at the website. I can see it requests DHCP, it gets an IP address (NATed), it does some measurements (like HTTP and NTP) successufly but at atlas.ripe.net it is listed as 'Never online'. It rebooted around 3 times in the last week and each time was kept as least 24h in a row with no power down or cable disconnect.
The MAC ADDRESS at the website matches with the MAC ADDRESS labeled in the probe.
How should I proceed to get this fixed?
Best regards,
Thiago Ayub
Hello, dead external USB flash can be also one of reasons (I had such issue). You can try replace it with new one. With regards, Daniel On 8.10.2015 03:28, Thiago Ayub wrote:
Hi,
I receive a week ago our first probe but I'm unable to make it appear as online at the website. I can see it requests DHCP, it gets an IP address (NATed), it does some measurements (like HTTP and NTP) successufly but at atlas.ripe.net it is listed as 'Never online'. It rebooted around 3 times in the last week and each time was kept as least 24h in a row with no power down or cable disconnect.
The MAC ADDRESS at the website matches with the MAC ADDRESS labeled in the probe.
How should I proceed to get this fixed?
Best regards,
Thiago Ayub
Hi, On Thu, Oct 08, 2015 at 10:08:23AM +0200, Daniel Suchy wrote:
dead external USB flash can be also one of reasons (I had such issue). You can try replace it with new one.
Yeah, the v3 probes seem to be a bit flakey in that regard - I have 3 of them, and two had flash that the box just did not like (but which seems to be working nicely elsewhere). Flash replaced, box happy. 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
Actually both the power and the USB memory issues can be related. I have "repaired" non-working flash by changing the power supply. Daniel
Hi, How can I repair the flash memory? Is there an image file online I can download it and write it to a new flash memory and insert it at the TP-Link device? Best regards, Thiago Ayub
Hi, On Thu, Oct 08, 2015 at 09:54:55AM -0300, Thiago Ayub wrote:
How can I repair the flash memory? Is there an image file online I can download it and write it to a new flash memory and insert it at the TP-Link device?
Turn off, remove flash stick, turn off (it will now boot from internal memory), after a few minutes, insert new flash stick, wait. For me, this was usually sufficient to get the boxes back to live. Also, you can look on the "my probes" page under "network", all the way down, for the last SOS DNS messages the probe sent - it will usually tell the system (via queries like "INO-USB.$probeid....ripe.net") what is wrong. 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
Also, you can look on the "my probes" page under "network", all the way down, for the last SOS DNS messages the probe sent - it will usually tell the system (via queries like "INO-USB.$probeid....ripe.net") what is wrong.
FYI: the log of these queries is exposed in the UI, at the bottom of the network tab of your probe status page. Cheers, Robert
That's the thing. There are no even SOS messages from that probe. In such cases one should double check the tcp/443 and DNS working before starting fiddling with the hardware. /vty On 10/8/15 3:10 PM, Robert Kisteleki wrote:
Also, you can look on the "my probes" page under "network", all the way down, for the last SOS DNS messages the probe sent - it will usually tell the system (via queries like "INO-USB.$probeid....ripe.net") what is wrong. FYI: the log of these queries is exposed in the UI, at the bottom of the network tab of your probe status page.
Cheers, Robert
participants (7)
-
Daniel Karrenberg -
Daniel Suchy -
Gert Doering -
Phillip Remaker -
Robert Kisteleki -
Thiago Ayub -
Viktor Naumov