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] Your probe is currently disconnected
- Previous message (by thread): [atlas] Your probe is currently disconnected
- Next message (by thread): [atlas] Your probe is currently disconnected
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
James Andrewartha
jandrewartha at ccgs.wa.edu.au
Thu Mar 2 04:23:50 CET 2017
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
- Previous message (by thread): [atlas] Your probe is currently disconnected
- Next message (by thread): [atlas] Your probe is currently disconnected
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]