Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Miles Lane <miles.lane@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Jouni Malinen <j@w1.fi>
Subject: Re: mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption"
Date: Thu, 03 Apr 2008 16:01:53 +0200	[thread overview]
Message-ID: <1207231313.3636.100.camel@johannes.berg> (raw)
In-Reply-To: <1207226756.3636.66.camel@johannes.berg> (sfid-20080403_135257_509725_35FED48D)

[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]


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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2008-04-03 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a44ae5cd0804021732s6ae5ed81ma5e229ae0faf4aaf@mail.gmail.com>
2008-04-03 12:45 ` mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption" Johannes Berg
2008-04-03 13:15   ` Miles Lane
2008-04-03 13:19     ` Johannes Berg
2008-04-03 13:24     ` Miles Lane
2008-04-03 13:30       ` Johannes Berg
2008-04-03 13:32         ` Miles Lane
2008-04-03 13:34           ` Johannes Berg
2008-04-03 13:36           ` Johannes Berg
2008-04-03 14:01   ` Johannes Berg [this message]
2008-04-03 16:52     ` Jouni Malinen
2008-04-03 17:14       ` Miles Lane
2008-04-04 14:51       ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1207231313.3636.100.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=jbenc@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox