Search Linux Wireless

Re: mac80211 / iwl3945 + dynamic wep (again)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> While I fully agree that these messages should be rate limited, it is
> somewhat surprising to see this large a number of reported ICV failures.
> Does the ipw3945 not filter out FCS errors before passing the frame for
> WEP decryption? Or is there something odd about this network/client
> configuration that makes the client try to decrypt frames that are not
> really for it?

I agree. We have the following chunk of code in the decrypt handler:

        /*
         * No point in finding a key and decrypting if the frame is neither
         * addressed to us nor a multicast frame.
         */
        if (!(rx->flags & IEEE80211_TXRXD_RXRA_MATCH))
                return TXRX_CONTINUE;

the RA_MATCH flag is cleared when the frame is neither multicast nor
addressed to us so I don't see how we can get into WEP decryption. A
concurrently running tcpdump might help though without the keys it'd be
hard to verify everything.

The fact that ipw3945 doesn't print out any such messages is hardly
indicative of a mac80211 problem btw, maybe it simply doesn't contain
such debug messages.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux