[Bugs] #1674 UNSP: change of encryption requirement on an access point prevents network connection

[Sugar Labs Bugs]

#1674: change of encryption requirement on an access point prevents network
connection
------------------------------------------+---------------------------------
    Reporter:  quozl                      |          Owner:                             
        Type:  defect                     |         Status:  assigned                   
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:  0.84.x                     
    Severity:  Minor                      |       Keywords:                             
Status_field:  New                        |   Distribution:                             
   Seeta_dev:                             |  
------------------------------------------+---------------------------------
Changes (by sascha_silbe):

  * distribution:  OLPC =>
  * severity:  Unspecified => Minor
  * status_field:  Unconfirmed => New


Comment:

 Just tried this on current git master with some of Quozls network patches
 applied (but not the one mentioned above). After changing the access point
 from WEP to open, the following behaviour can be observed:

  1. The wifi LED turns off (indicating no connection to AP), but the old
 icon still has the "connected" badge.
  1. The wifi LED blinks a few times (indicating scanning).
  1. A new icon with a color different from the old icon, but with a
 "favourite star" badge appears.
  1. After some time the old icon looses the "connected" badge and starts
 pulsing.
  1. The key dialog appears, asking for WEP credentials.
  1. After cancelling the dialog, the old icon stops pulsing, but still
 shows the "favourite star" badge.
  1. After clicking the '''new''' icon, the '''old''' icon starts pulsing.
  1. The key dialog appears, asking for WEP credentials.

 Analysis:

 The reason for showing a new icon probably is that
 {{{jarabe.model.network.AccessPoint.network_hash()}}} returns a different
 hash for networks with the same SSID, but different security settings.
 This seems to be on purpose.

 For connecting to the network, however,
 {{{jarabe.desktop.networkviews.WirelessNetworkView._connect()}}} looks up
 the connection from the Sugar-side NetworkManager User Settings service
 using only the SSID:

 {{{
     def _connect(self):
         connection = network.find_connection_by_ssid(self._name)
         if connection is None:
           [create connection object, add it to User Settings service]
 [...]
 }}}

 This will yield the old "connection" instance, including security
 settings. NetworkManager obediently tries to connect using WEP and fails.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/1674#comment:11>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system