Your probe is currently disconnected
Hi! I've applied for an Atlas probe v3 and got one via postage. So, I've connected the probe to my network. I can see in my DNSMasq logs, that the probe gets successfully an IP address. It can be pinged without any problems. But that's all. Even after 24 hours it's still reported not connected. I can see multiple LEDs: 1 (power): on 2: off 3: slow blink 4: fast blink 5 (button): on I can't find that in the FAQ, the LEDs should light different. The FAQ also did mention to try first without USB and insert USB later. Or try to replace the USB. Both cases did not help. If I connect my ThinkPad instead the probe with the same network connection (cable and port), it can access the internet just fine without any problems.. I've no clou, what could be wrong. Any ideas? Thanks! Conrad Viele Grüße Conrad Kostecki
Hi Conrad, On 02/03/17 07:39, Conrad Kostecki wrote:
So, I've connected the probe to my network. I can see in my DNSMasq logs, that the probe gets successfully an IP address. It can be pinged without any problems.
But that's all. Even after 24 hours it's still reported not connected. [snip LEDs] The FAQ also did mention to try first without USB and insert USB later. Or try to replace the USB. Both cases did not help.
How long did you leave it booting without the USB before plugging it in? In your probe's network tab on the website, do you see anything in the SOS history? My probe that I received in January also didn't connect automatically, I had to follow the re-initialisation procedure for it to connect. Thanks, -- James Andrewartha Network & Projects Engineer Christ Church Grammar School Claremont, Western Australia Ph. (08) 9442 1757 Mob. 0424 160 877
Hi James! Am 02.03.2017 04:23:50, "James Andrewartha" <jandrewartha@ccgs.wa.edu.au> schrieb:
How long did you leave it booting without the USB before plugging it in? In your probe's network tab on the website, do you see anything in the SOS history? The last time, I've waited about 24 hours. I've plugged it now again without the usb stick, 2 hours ago.
So without an usb stick, it always should list at least a SOS message? Because, after the 2 hours now, it's still marked as disconnected. Conrad Viele Grüße Conrad Kostecki
On 2017-03-02 11:23, Conrad Kostecki wrote:
Hi James!
Am 02.03.2017 04:23:50, "James Andrewartha" <jandrewartha@ccgs.wa.edu.au> schrieb:
How long did you leave it booting without the USB before plugging it in? In your probe's network tab on the website, do you see anything in the SOS history? The last time, I've waited about 24 hours. I've plugged it now again without the usb stick, 2 hours ago.
So without an usb stick, it always should list at least a SOS message? Because, after the 2 hours now, it's still marked as disconnected.
Conrad
Viele Grüße Conrad Kostecki
Hi, The probe should send SOS messages at each boot regardless of having a USB stick or not. However, it cannot connect to the infrastructure without one, as it does not have the needed firmware. You need to insert one a few minutes after booting. In case that doesn't help, our staff may be able to help you further if you send mail to atlas@ripe.net mentioning your probe's ID. Regards, Robert
On 2017-03-01 at 19:39, Conrad Kostecki wrote:
So, I've connected the probe to my network. [...] If I connect my ThinkPad instead the probe with the same network connection (cable and port), it can access the internet just fine without any problems.. I've no clou, what could be wrong. Any ideas?
Unlikely, but possible: The router/modem could restrict network access by MAC address. That could explain why one device (laptop) can connect, while another (probe) can not. Unlikely, but worth checking. BR Daniel AJ
On 2 March 2017 at 11:56, Daniel AJ Sokolov <listclient@sokolov.eu.org> wrote:
On 2017-03-01 at 19:39, Conrad Kostecki wrote:
So, I've connected the probe to my network. [...] If I connect my ThinkPad instead the probe with the same network connection (cable and port), it can access the internet just fine without any problems.. I've no clou, what could be wrong. Any ideas?
Unlikely, but possible: The router/modem could restrict network access by MAC address. That could explain why one device (laptop) can connect, while another (probe) can not.
This is a very possible - the USB key hardware fault can cause exactly this behaviour.
Hello Daniel, Am 02.03.2017 05:56:02, "Daniel AJ Sokolov" <listclient@sokolov.eu.org> schrieb:
Unlikely, but possible: The router/modem could restrict network access by MAC address. That could explain why one device (laptop) can connect, while another (probe) can not.
Unlikely, but worth checking.
Nope ;-) This is my home network here, I don't have any restriction by MAC. Conrad
Am 02.03.2017 00:39:08, "Conrad Kostecki" <ck+atlasripe@bl4ckb0x.de> schrieb:
Any ideas? I've found the cause. It was a small typo for the assigned DNS server via DHCP. After setting the correct one, the probe is now working correctly.
But it's strange, because the wrong DNS is also reachable via ThinkPad, but is in a different subnet. It should have worked with the probe. Anyway, it's working now. Cheers Conrad
Dear Conrad, Your Name and Website has turned up in a HSTS Plist coocies file on my Mac, along with the names and websites of many other hacker Websites, and i wonder why. I am not a Hacker, but my friend in Singapore is Chief Comissioner of the Cybercrime Division, and i wanted to ask you before sending all the data i have to hjim (including the info about you which is in my HSTS plist and all its redirects), if you have a moral and decent explanation for why your websites and scripts seem to be trying to invade my mac? Otherwise i shall be forced to send the data to my friend at the International Cybercrime Division of Singapore, for him to investigate for me. Please explain why you are in my binary cookies and hsts plists? Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
Hi Spencer This is clearly the wrong forum. Not sure if you are trolling or not.. Anyone can submit their domains to the HSTS preload list: list, and if the domain live up to the requirements, it will be included in the HSTS preload list, and hardcoded (compiled) in the next browser release. No one is hacking your Mac. https://hstspreload.org/ https://tools.ietf.org/html/rfc6797 Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
participants (7)
-
Conrad Kostecki -
Daniel AJ Sokolov -
Emil Stahl -
James Andrewartha -
Jonathan Brewer -
Robert Kisteleki -
Spencer Littlewood