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>
Subject: Re: mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption"
Date: Thu, 03 Apr 2008 14:45:56 +0200 [thread overview]
Message-ID: <1207226756.3636.66.camel@johannes.berg> (raw)
In-Reply-To: <a44ae5cd0804021732s6ae5ed81ma5e229ae0faf4aaf@mail.gmail.com> (sfid-20080403_013238_466005_CF563BE7)
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
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
> ./rx.c: printk(KERN_DEBUG "%s: RX non-WEP frame, but expected "
> 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
>
> I am wondering whether this indicates a problem situation with the
> access point that really needs to be reported. Is this being reported
> because it is a security risk? Is this a condition that really needs
> to be reported by wireless drivers?
Hm. You shouldn't actually be getting this when your AP is configured to
use encryption. It either points to somebody trying to invade your
network (unlikely) or an AP bug.
Can you use 'iw' to add a new monitor interface and capture some of the
unencrypted packets with that? Use
$ git clone http://git.sipsolutions.net/iw.git/
$ cd iw
$ make
# ./iw dev wmaster0 interface add moni0 type monitor
and then wireshark/tcpdump on it, you can also send me the dump in
private mail if you cannot identify the problem. If you *disable* hw
crypto I won't even be able to read your actual traffic :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2008-04-03 12:52 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 ` Johannes Berg [this message]
2008-04-03 13:15 ` mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption" 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
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=1207226756.3636.66.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--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