#4818 HIGH Never A: XOs saturate wireless network

[Zarro Boogs per Child]

#4818: XOs saturate wireless network
--------------------------------+-------------------------------------------
  Reporter:  wmb at firmworks.com  |       Owner:  mbletsas      
      Type:  defect             |      Status:  closed        
  Priority:  high               |   Milestone:  Never Assigned
 Component:  wireless           |     Version:                
Resolution:  duplicate          |    Keywords:                
  Verified:  0                  |  
--------------------------------+-------------------------------------------

Comment(by rsavoye):

 Comments from the Hacker's Conference list that I posted this morning.
 Sorry, I've been on vacation, driving home 1300 miles form the conference.
 There were 2 B4s, and 1 B2 at the conference involved in this problem.

 > > can somebody who knows post here an explanation on why the
 > > OLPCs were rendering the wifi network unusuable, and if the

 Several folks, including myself, spent time trying to track this down.
 I'll
 add full details to the bug report on dev.laptop.org after I get home from
 Hackers. (I've been driving back to CO) We believe the problem is related
 to
 having multiple APs with the same SSID, all in a small area. (9 of them
 within
 200 feet). I'll try to test this when I get back.

 I've had OLPCs in other dense networks, like Chaos Camp, with zero
 problems,
 but there all the APs had unique SSIDs. There were also multiple OLPCs. As
 they were all running build 406, where the mesh code doesn't even fully
 work, it's
 odd there was a problem at all.

 > > rumour that they do it even when not connected to the network,
 > > just by being powered on is true?

 The problem was people kept rebooting the OLPCs, as they often didn't
 know how to close running applications, which restarted the mesh network
 after I had shut it down.

-- 
Ticket URL: <http://dev.laptop.org/ticket/4818#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system