<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<body text="#000000" bgcolor="#FFFFFF">
Following some advices received by email, I booted it without USB
then inserted USB stick 10 minutes later, and it worked. Probably
stock firmware has some problem detecting USB devices during boot
cycle. In any case, problem is solved for now.<br>
With Best Regards,
<!-- signature end --></div>
<div class="moz-cite-prefix">On 27/01/16 14:54, Marco Slater wrote:<br>
<pre wrap="">Hi Marat,
I noticed information started to show up on the panel when it started its few reboot loops. After that it kept loosing network connectivity, even though it was there, which showed up on the panel, it would connect/disconnect to the atlas control servers constantly for at least a day, after which it just stopped and stabilised.
If someone can let me know if theres any way to restore logs or any hint as to what exactly happened on my probe, I have no problem taking a look and sharing my findings, even though it seems to work fine now, so far. If it helps, the probe ID for the one of mine which had said issues is 19100 .
Hope this helps in some way. :)
<pre wrap="">On 27 Jan 2016, at 10:42, Marat Khalili <a class="moz-txt-link-rfc2396E" href="mailto:email@example.com"><firstname.lastname@example.org></a> wrote:
Thank you very much for your reply. I'll try to leave it as is until Monday.
Do you remember if there was any information about the probe's IP address on the Network tab during that time?
With Best Regards,
On 27/01/16 13:27, Marco Slater wrote:
I’ve had a similar issue where the probe just wouldn’t come online, or detect anything.
All I did is leave it there for a few days, it started coming online and going offline constantly every few minutes for the second day, and then it just sorted itself, I noticed I got an alert on the “Messages” tab saying the probe upgraded its firmware and kernel, it’s been working fine since.
Not sure if its related at all, would be nice if you could get some more debugging out of probes. :)
I didn’t really question it until now, but it does seem odd.
<pre wrap="">On 27 Jan 2016, at 10:10, Marat Khalili <a class="moz-txt-link-rfc2396E" href="mailto:email@example.com"><firstname.lastname@example.org></a>
I have received my probe yesterday morning (V3, like shown on
<a class="moz-txt-link-freetext" href="https://atlas.ripe.net/docs/probe-v3/">https://atlas.ripe.net/docs/probe-v3/</a>
), connected and registered it. Unfortunately, not only no measurements or IP address information appeared in my profile after waiting several hours, but there's no Ethernet activity from probe at all, even in the packet trace.
Things I tried:
* 3 different switches (Fast and Gigabit types); in all cases a notebook running either Windows or Ubuntu when connected into the same socket acquires IP address just fine and can browse the Internet.
* 3 different LAN cables; in all cases switches detect 100 Mbps physical wire but nothing more.
* 2 different DHCP servers as well as wireshark on direct connection.
* 3 different power sources (1A phone charger, notebook 2xUSB, PC USB).
* Removing and re-inserting the USB flash key that came with the device, dd'ing its contents to a different USB flash and inserting it instead (dd finished successfully).
Every time after the boot sequence ends first light glows steadily and adjacent one blinks slowly, like it is supposed to be according to
<a class="moz-txt-link-freetext" href="https://atlas.ripe.net/about/faq/#what-do-the-lights-on-the-side-of-the-probe-mean">https://atlas.ripe.net/about/faq/#what-do-the-lights-on-the-side-of-the-probe-mean</a>
. Looks like the interface just isn't up in the device OS. Is there anything else I can check? Should I request another probe? (it took more than month to receive first one by post)
With Best Regards,