#6191 HIGH Never A: WPA fails

[Zarro Boogs per Child]

#6191: WPA fails
-----------------------+----------------------------------------------------
  Reporter:  bert      |       Owner:  dwmw2         
      Type:  defect    |      Status:  new           
  Priority:  high      |   Milestone:  Never Assigned
 Component:  wireless  |     Version:                
Resolution:            |    Keywords:  Update.1?     
  Verified:  0         |    Blocking:                
 Blockedby:            |  
-----------------------+----------------------------------------------------

Comment(by yani):

 Replying to [comment:10 garyo]:

 > Can I help debug this any more?  I don't know how to use wpa_supplicant
 on olpc, for instance (so I can't say whether it would work that way).

 Try this(it was posted from Ricardo some time ago):
 -----------
 killall NetworkManager
 if [ -e /etc/wpa_supplicant/wpa_suplicant.conf ]; then
  rm /etc/wpa_supplicant/wpa_suplicant.conf
 fi
 wpa_passphrase <ssid> <passphrase> >
 /etc/wpa_supplicant/wpa_supplicant.conf
 wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf
 dhclient eth0
 -----------

 > It ''seems'' to me that it only connects if I turn on the machine, wait
 a really long time for it to go around to all the mesh blue dots (1, 6,
 11) -- none of which are really meshes (nobody near me has another XO) and
 after they all time out a few times it stops trying.  Then and only then
 can I click the WPA net and it'll succeed; pretty quickly when it does
 work.

 You should know that you dont need many XOs to connect to a mesh channel.
 Having connected to e.g. mesh 1 only means that you are setup to detect/be
 detected by other XOs that are also connected to mesh 1.
 A blue dot(1 ,6 ,11) does NOT mean that there is an active populated mesh
 waiting for you.
 This concept is not very clear in the mesh view, because the mesh circles
 are treated equally with the AP circles, in fact they are completely
 different.

 If you want your XO to connect directly to your AP, try the following
 $echo infra > /etc/NetworkManager/mesh-start

 check this out for more info:
 http://wiki.laptop.org/go/Test_Config_Notes#Testing_of_Different_Connection_Configurations

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