#3990 BLOC Trial-3: New install of 611 doesn't connect to WEP

[Zarro Boogs per Child]

#3990: New install of 611 doesn't connect to WEP
------------------------------+---------------------------------------------
  Reporter:  kimquirk         |       Owner:  dcbw   
      Type:  defect           |      Status:  new    
  Priority:  blocker          |   Milestone:  Trial-3
 Component:  network manager  |     Version:         
Resolution:                   |    Keywords:         
  Verified:  0                |  
------------------------------+---------------------------------------------

Comment(by dcbw):

 Do what you want; but I'd argue against retries.  What's different about
 OLPC and Apple?  I believe that adding text to the dialog box is
 sufficient.  Apple doesn't have text in their dialog, why should OLPC?
 Why can this not just be release noted?

 Retrying the association attempt with a rehashed key just sucks for all
 the reasons that we keep bitching about with mesh already.  It's going to
 take a long time and the user will have no idea what's happening.
 Potentially a minute or so to connect to the access point.  It would also
 be a bunch of code to notice that a certain attempt failed, pinpoint the
 cause of that failure, and try that exact same AP again. Again, with WEP
 you really have no idea what failed; did the DHCP just decide to go away?
 Are you on the margins of the AP's range?  Or is the WEP key really
 wrong?.

 Every single time that passphrase vs. hex key comes up, not just with
 OLPC, the people who want to the other method speak loudly.  And so
 behavior gets changed to make it easier there, and the other side speaks
 up loudly.  My believe is that passphrases (as they are mostly standard
 and are implemented everywhere) are the most common variant of WEP
 security input, and that hex keys are a fallback.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3990#comment:4>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system