#4858 HIGH Update.: XO doesn't see my access point

[Zarro Boogs per Child]

#4858: XO doesn't see my access point
-----------------------+----------------------------------------------------
  Reporter:  gdesmott  |       Owner:  mbletsas                         
      Type:  defect    |      Status:  reopened                         
  Priority:  high      |   Milestone:  Update.1                         
 Component:  wireless  |     Version:  Development build as of this date
Resolution:            |    Keywords:                                   
  Verified:  0         |  
-----------------------+----------------------------------------------------

Comment(by mbletsas):

 OK, did some testing and it seems that we have blamed the correct thing
 for the wrong reasons. This is indeed yet another consequence of the
 lazyWDS mess.

 Briefly, certain lazyWDS-capable access points (like the various versions
 of the WRT54), start using WDS frames for all communications with wlan
 cards that they observe emitting WDS frames (like the XOs). This means
 that the XO sends a normal infrastructure frame to the AP and the AP
 responds back with a WDS frame.

 We compensate for that on the XO side in order to be able to use such APs,
 however at this point it seems that the beacons emitted from such APs fall
 victim to the BSSID filtering that we have to do.


 Wireless firmware  versions 5.110.19.x, don't have the compensation in
 place and because of that they can always see the beacons from the WRT54s

 Firmware versions 5.110.18.x and 5.110.20.p3+ will see the beacons when
 they first boot up and before the AP notices that they emit WDS frames and
 switches to WDS.

 So if you just have one XO, you can try to shutoff the XO, then powercycle
 the WRT54 then try to associate with it (you should be able to see it in
 the neighborhood view).

 M.

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