[Server-devel] Large groups of XO-1 do not work with access points

Anna aschoolf at gmail.com
Fri Feb 7 23:57:41 EST 2014

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 repeatedly don't automatically see a
couple of my AP's in Sugar's Network Neighborhood on boot (some of my XO-1
units "just work," btw).  In a console, I'll do `iwlist eth0 scan |grep <my
ap's ssid>` multiple times until it shows up (or grep on ESSID for the list
of what all it sees).  Then switch back to Network Neighborhood, find the
AP's "circle" (which now shows up) and associate.

After that, networking is fine until reboot, but then I just repeat the
above procedure.

What I found peculiar was that the AP doesn't initially show up on those
XO-1's even when the XO-1 is on the table right next to the AP.  But, hey,
I figured out how to scan for it and then moved on.  I didn't know others
had this issue in other environments.

My home environment is relatively noisy.  I'm looking at an XO-1 now and it
can see 16 APs: four on channel 1, one on channel 4, one on channel 5,
three on channel 6, three on channel 8, one on channel 10, three on channel
11.  Only three of those are in my house - Tyler's AP on channel 1 (which
is WPA encrypted and I don't typically use), my "regular AP" on channel 11,
and the XSCE's AP on channel 6.

Musing upon it now, I should probably switch the channels between my
"regular AP" on 11 and the XSCE's - the XSCE's channel 6 might be getting
crowded out by my neighbors on 4,5,6, and 8.


On Fri, Feb 7, 2014 at 7:21 PM, James Cameron <quozl at laptop.org> wrote:

> On Sat, Feb 08, 2014 at 12:16:06PM +1100, James Cameron wrote:
> > 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,
> This implies a problem in the firmware or the kernel.
> --
> James Cameron
> http://quozl.linux.org.au/
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/server-devel/attachments/20140207/9ea65407/attachment.html>

More information about the Server-devel mailing list