#10156 NORM 1.5-sof: association with wrong AP after wakeup

[Zarro Boogs per Child]

#10156: association with wrong AP after wakeup
---------------------------------------+------------------------------------
           Reporter:  pgf              |       Owner:  dsd                               
               Type:  defect           |      Status:  new                               
           Priority:  normal           |   Milestone:  1.5-software-later                
          Component:  network manager  |     Version:  Development source as of this date
         Resolution:                   |    Keywords:                                    
        Next_action:  never set        |    Verified:  0                                 
Deployment_affected:                   |   Blockedby:                                    
           Blocking:                   |  
---------------------------------------+------------------------------------

Old description:

> two APs are in view, both have been connected to successfully in the
> past.  first A was connected to, then B.
>
> while laptop is associated with B, put it to sleep with power button or
> lid.
>
> wake it up.  laptop reassociates with A.
>
> preference should be given to AP most recently associated with.
> (i don't know if this is completely repeatable:  i.e., i don't know
> whether the AP chosen is based on order of original discovery, or
> random.)

New description:

 two APs are in view, both have been connected to successfully in the past.
 first A was connected to, then B.

 while laptop is associated with B, put it to sleep with power button or
 lid.

 wake it up.  laptop reassociates with A.

 preference should be given to AP most recently associated with.
 (i don't know if this is completely repeatable:  i.e., i don't know
 whether the AP chosen is based on order of original discovery, or random.)

--

Comment(by Quozl):

 No, it's not necessarily NetworkManager's fault.

 Sugar provides to NetworkManager a list of the connections that
 NetworkManager can choose to connect to.  This list is sorted in user
 selection order.

 (This is unlike GNOME ''nm-applet'' which uses the System Settings for
 connections, see SL 1884).

 In the scenario described in this ticket #10156, at the time the laptop
 resumes, NetworkManager has this list:

 ||ssid||
 ||A||
 ||B||

 And no wireless device.

 Both networks have been activated for connection by Sugar.  The situation
 as seen by NetworkManager is ambiguous.  A new wireless device has just
 appeared.  Which network should be tried?

 NetworkManager tries A before B.  I presume it tries in the same order it
 was originally asked to try.  Once it achieves a connection, it stops
 trying.

 The same list is given to NetworkManager when Sugar starts, which is what
 happened in #10121.

 The problem can be solved by separating the list of saved passphrases (in
 Sugar) from the list of connections requested (in Sugar, given to
 NetworkManager).

 I've had a go at it but it proved an excessive degree of change for 0.84.

 The problem can also be solved by using the System Settings for
 connections (SL 1884).  This seems the more appropriate solution.

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