#7480 BLOC 8.2.0 (: Need to 'reset' the network configurations - short term fix
Zarro Boogs per Child
bugtracker at laptop.org
Thu Aug 21 13:28:22 EDT 2008
#7480: Need to 'reset' the network configurations - short term fix
------------------------+---------------------------------------------------
Reporter: kimquirk | Owner: erikg
Type: defect | Status: assigned
Priority: blocker | Milestone: 8.2.0 (was Update.2)
Component: sugar | Version: Update.1
Resolution: | Keywords: 8.2.0:? blocks:8.2.0 r-
Next_action: code | Verified: 0
Blockedby: | Blocking:
------------------------+---------------------------------------------------
Comment(by erikg):
Replying to [comment:24 cscott]:
> Note that the root cause of this bug is different: nminfo.py assumes
that all networks named 'linksys' are the same, and ignores the BSSID
(http://en.wikipedia.org/wiki/SSID). Once you associate with one network
named 'linksys' and use a password, you can not longer associate with any
other network named 'linksys' with a different (or no) password.
>
> The easiest solution is to make nminfo.py key off ESSID+BSSID, not just
essid. This errs conservatively if you're in a large institution with a
legimate password-protected ESSID which spans multiple BSSIDs and
reprompts for the password, but this seems much safer than the current
behavior.
> I'd prefer fixing this bug for 8.2 by keying off BSSID, which doesn't
require adding new UI.
This is a classic case of not understanding the problem before jumping in
to fix it. I am in error in that effort. I wish I had come to understood
this specific description of the problem sooner (all linksys routers being
treated similarly because of the keying used in the networks.cfg). It is
not a good idea to implement a UI change to enact this. I agree that we
should change nminfo.py to reflect ESSID+BISSID instead of just ESSID.
--
Ticket URL: <http://dev.laptop.org/ticket/7480#comment:26>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list