#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:                   |  
---------------------------------------+------------------------------------

Comment(by dsd):

 Replying to [comment:3 Quozl]:
 > (This is unlike GNOME ''nm-applet'' which uses the System Settings for
 connections, see SL 1884).

 That's not true - it runs its own settings service, like sugar, unless you
 tick a certain box in one of the advanced per-connection dialogs in which
 case the system service is used for that specific connection.

 > 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.

 Could well be the case that it tries them in order.

 > 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'm not so sure.
 If the user connects to A, then B, then suspends, both of those connection
 objects will be on the bus, and NM might pick A instead of B.

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

 At least in Fedora, the system settings service doesn't support WPA/WPA2
 without some special configuration that moves it away from the Fedora
 style config into a NM-specific beast. (It would of course be easy to set
 up this configuration on every distribution of Sugar, but it's a bit
 questionable IMO)

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