#8400 NORM Not Tri: Cannot associate with WAP via WEP

[Zarro Boogs per Child]

#8400: Cannot associate with WAP via WEP
----------------------------+-----------------------------------------------
   Reporter:  hhardy        |       Owner:               
       Type:  defect        |      Status:  new          
   Priority:  normal        |   Milestone:  Not Triaged  
  Component:  not assigned  |     Version:  not specified
 Resolution:                |    Keywords:               
Next_action:  never set     |    Verified:  0            
  Blockedby:                |    Blocking:               
----------------------------+-----------------------------------------------

Comment(by hhardy):

 Henry:

 Here's some information on my wireless access point for your report. Let
 me know if you need more...

 MAKE: Netgear
 MODEL: WAG102
 DESCRIPTION: ProSafe Dual Band Wireless Access Point
 FIRMWARE VERSION: V2.0.7NA

 We were trying to get your OLPC XO to connect to it on wireless standard
 802.11g, channel 10, with a broadcast SSID, using WEP security at 128-bit
 encryption with a shared key.

 The only thing I notice now as I'm looking over the security profile I set
 up is that I might have mistakenly said that the WAP was on channel 11 at
 the time, when it looks like it was on channel 10. I got confused by the
 fact that the standard security profile names include "11" to indicate
 "802.11." This shouldn't have made a difference unless you were specifying
 the channel on your end, though.

 Regards,


 Mark


 Mark Ziemba
 markziemba at sbcglobal.net

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