#2373 HIGH Untriag: Clicking on an AP in the mesh view didn't change XO connection

[Zarro Boogs per Child]

#2373: Clicking on an AP in the mesh view didn't change XO connection
------------------------------+---------------------------------------------
  Reporter:  kimquirk         |       Owner:  dcbw     
      Type:  defect           |      Status:  new      
  Priority:  high             |   Milestone:  Untriaged
 Component:  network manager  |     Version:           
Resolution:                   |    Keywords:           
  Verified:  0                |  
------------------------------+---------------------------------------------
Old description:

> B4, build 528.
>
> I first booted up my XO at home where it couldn't find a school server.
> It had only local mesh connection and was able to find other local mesh
> laptops.
>
> Then I clicked on my WEP enabled infrastructure AP, supplied the
> password, and it was able to connect.
>
> The other laptops could no longer connect to this one, so decided to shut
> them all down and try again. After rebooting the first laptop could no
> longer connect to my WEP AP.

New description:

 B4, build 528.

 I first booted up my XO at home where it couldn't find a school server. It
 had only local mesh connection and was able to find other local mesh
 laptops.

 Then I clicked on my WEP enabled infrastructure AP, supplied the password,
 and it was able to connect.

 The other laptops could no longer connect to this one, so decided to shut
 them all down and try again. After rebooting the first laptop could no
 longer connect to my WEP AP.

 From the mesh view I clicked on an open AP in hopes that the problem was
 related to WEP, but the icon for the WEP AP continued to flash (like it
 was still trying); and the iwconfig showed that it was still connecting to
 the WEP AP.

-- 
Ticket URL: <https://dev.laptop.org/ticket/2373#comment:1>
One Laptop Per Child <http://laptop.org/>