#651: unable to associate to AP using WEP with madwifi-ng
-------------------------------------------+--------------------------------
      Reporter:  [EMAIL PROTECTED]  |       Owner:  mentor                      
                       
          Type:  defect                    |      Status:  assigned             
                              
      Priority:  major                     |   Milestone:  version 0.9.x - 
progressive release candidate phase
     Component:  madwifi: other            |     Version:  trunk                
                              
    Resolution:                            |    Keywords:  associating fails    
                              
Patch_attached:  1                         |  
-------------------------------------------+--------------------------------
Comment (by brian):

 My analysis of the captured data was way off base.  I was misled by the
 format of the captured packets.  The "+recv" debugging output was
 appending an extra 4 bytes to every frame, containing the frame checksum.
 The ethereal packet decoders were not expecting the frame checksum, and so
 reported a bogus packet.  (I submitted a fix to madwifi a few days ago so
 that the frame checksums are not logged any longer.)

 I looked at your packet captures again, this time stripping off the extra
 4 bytes before asking ethereal to decode the packet.  This is what
 tethereal shows:

 IEEE 802.11
     Type/Subtype: Authentication (11)
     Frame Control: 0x00B0 (Normal)
         Version: 0
         Type: Management frame (0)
         Subtype: 11
         Flags: 0x0
             DS status: Not leaving DS or network is operating in AD-HOC
 mode (To DS: 0 From DS: 0) (0x00)
             .... .0.. = More Fragments: This is the last fragment
             .... 0... = Retry: Frame is not being retransmitted
             ...0 .... = PWR MGT: STA will stay up
             ..0. .... = More Data: No data buffered
             .0.. .... = Protected flag: Data is not protected
             0... .... = Order flag: Not strictly ordered
     Duration: 258
     Destination address: PhilipsC_4c:a0:97 (00:05:4e:4c:a0:97)
     Source address: Agere_61:cc:94 (00:02:2d:61:cc:94)
     BSS Id: Agere_61:cc:94 (00:02:2d:61:cc:94)
     Fragment number: 0
     Sequence number: 2651
 IEEE 802.11 wireless LAN management frame
     Fixed parameters (6 bytes)
         Authentication Algorithm: Unknown (20717)
         Authentication SEQ: 0x0004
         Status code: Authentication rejected because of challenge failure
 (0x000f)

 I know you wrote that you have this working with madwifi-old, but is it
 possible that your script is specifying the wrong WEP key?

-- 
Ticket URL: <http://madwifi.org/ticket/651>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets

Reply via email to