G'day Anne,
Yes, a manual "sudo iwlist eth0 scan" in Terminal, or an "iwlist eth0
scan" in console, until the AP appears, is all it takes to fix. You
derived an independent workaround for the same problem!
If you have some XO-1 that work and some that don't, then you might
have one broken antenn
This is all very interesting, particularly when James Cameron stated,
"...all it takes is for two active scans to miss the access point." All
the years I've been working with these things, I really had no idea. And
did I inadvertently do the correct workaround?
I've got a couple of XO-1's that r
There seems to be a lot of speculation, so I'll add more technical
details on what Terry and I have been investigating.
1. sometimes, an active scan by the XO-1 does not have the access
point listed in the scan results, despite the XO-1 transmitting an
acknowledgement to the access point,
2. an
On
https://docs.google.com/document/d/1o6QtzLb6e58YKWqMf_junux2XyBRLFm31un8YLcYslg
Anna, Ben, Jon, Martin, Adam, Tim, TK, and Tom wrote:
> Very confounding Wifi: while connecting initially, large numbers of
> XO-1s fail to (re?)associate with Village Telco / Mesh Potato and
> other AP’s. Even whi
