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 15:30:07 +0200 [thread overview]
Message-ID: <1207229407.3636.79.camel@johannes.berg> (raw)
In-Reply-To: <a44ae5cd0804030624u40be9ad9rb1cadefadb13f889@mail.gmail.com> (sfid-20080403_142500_363034_CE408D97)
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Thu, 2008-04-03 at 09:24 -0400, Miles Lane wrote:
> Thanks. I think I have a working build, but can you confirm that the
> linker messages are benign?
Yeah, seems ok, as long as it runs :)
> I will get to work now on getting the log for you.
I'm about to go offline now, I'll look at it tomorrow. You should be
able to identify the packet that caused the problem in wireshark by
adding a display filter like "wlan.fc.protected == 0"
> CC iw.o
> cc: -lnl: linker input file unused because linking not done
Hrm. Yes, my mistake, I suppose. I don't like Makefile hacking :) Maybe
I should just go back to the built-in rules.
> interface.c: In function 'handle_interface':
> interface.c:64: warning: 'err' may be used uninitialized in this function
> interface.c:64: note: 'err' was declared here
> interface.c:138: warning: 'err' may be used uninitialized in this function
> interface.c:138: note: 'err' was declared here
Strange. I don't get those, and I don't know how the compiler arrives at
that conclusion.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-04-03 13:30 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 [this message]
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=1207229407.3636.79.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