From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: Miles Lane <miles.lane@gmail.com>, Jiri Benc <jbenc@suse.cz>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption"
Date: Fri, 04 Apr 2008 16:51:11 +0200 [thread overview]
Message-ID: <1207320671.19189.36.camel@johannes.berg> (raw)
In-Reply-To: <20080403165255.GI2025@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
> > Duration: 44
> What's wrong with the duration field value? The dump here does not
> indicate which transmit rate was used, so I don't know what TX rate the
> ACK would use, but 44 sounds like a reasonable duration value for
> 802.11g rates..
Yes, you're perfectly right, my rough estimate was totally off, I
miscalculated.
> > Does anybody have an explanation for that except that the AP software is
> > messing it up?
>
> Looks like an interesting AP behavior to me..
For some values of interesting... :)
> > In any case, I suppose the message in question isn't actually necessary.
> > I'll make it depend on verbose debugging maybe.
>
> Yes, that sounds reasonable. The AP should not be sending this kind of
> crap, but well, what can you do if it does.. In theory, this could also
> be showing up in multi-SSID configuration when another SSID is
> configured to use unencrypted frames (though, that would cause interop
> issues in association for number of clients..).
That would be ... interesting. But yeah, the message doesn't have much
value, it just tells you your peer might be buggy...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-04-04 14:51 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
2008-04-03 16:52 ` Jouni Malinen
2008-04-03 17:14 ` Miles Lane
2008-04-04 14:51 ` Johannes Berg [this message]
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=1207320671.19189.36.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