Search Linux Wireless

Re: mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption"

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

 



On Thu, 2008-04-03 at 14:45 +0200, Johannes Berg wrote:
> Hi,
> 
> Please copy the mailing list, I've done that now.
> 
> > My log files are filling up with these messages:
> > 
> >        [ 8722.198929] wlan0: RX non-WEP frame, but expected encryption
> >        [ 8726.506345] __ratelimit: 14 messages suppressed

> > It seems that others who are using Netgear WPN824 access points are
> > also seeing these messages in their logs.
> > http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1614
> > http://ubuntuforums.org/showthread.php?t=637084

Ok, I got packets from Miles, and this is what I found:

IEEE 802.11 Data, Flags: ......F.
    Type/Subtype: Data (0x20)
    Frame Control: 0x0208 (Normal)
        Version: 0
        Type: Data frame (2)
        Subtype: 0
        Flags: 0x2
            DS status: Frame from DS to a STA via AP(To DS: 0 From DS: 1) (0x02)
            .... .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: 44
    Destination address: <his STA MAC>
    BSS Id: <his Netgear AP>
    Source address: <his Netgear AP>
    Fragment number: 0
    Sequence number: 3874
Logical-Link Control
    DSAP: NULL LSAP (0x00)
    IG Bit: Individual
    SSAP: NULL LSAP (0x00)
    CR Bit: Command
    Control field: I, N(R)=0, N(S)=0 (0x0000)
        0000 000. .... .... = N(R): 0
        .... .... 0000 000. = N(S): 0
        .... .... .... ...0 = Frame type: Information frame (0x0000)
Data (1472 bytes)

0000  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
* all zeroes
05b0  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
    Data: 000000000000000000000000000000000000000000000000...


Note how the LLC header is also all-zeroes. Also note how the duration
field is totally bogus. The sequence number is actually correct.

Does anybody have an explanation for that except that the AP software is
messing it up?

In any case, I suppose the message in question isn't actually necessary.
I'll make it depend on verbose debugging maybe.

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