From: Johannes Berg <johannes@sipsolutions.net>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: Marshaling issues w/ compat-wireless-2010-08-19
Date: Wed, 25 Aug 2010 10:11:01 +0200 [thread overview]
Message-ID: <1282723861.3685.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4C746F74.70401@redfish-solutions.com>
On Tue, 2010-08-24 at 18:18 -0700, Philip Prindeville wrote:
> (1) "Unknown event 5" messages when starting up hostapd (line 95
> below):
That's fine, it's just EVENT_INTERFACE_STATUS.
> (2) Some highly unlikely values from the hostapd debugging messages
> when parsing out WEP authentication messages (line 507):
>
> This is captured in http://pastebin.ca/1924659 :
>
> authentication: STA=f8:1e:df:1e:c2:23 auth_alg=35510 auth_transaction=79 status_code=21688 wep=1
> Unsupported authentication algorithm (35510)
>
>
> I'm wondering if some messages that are passed up to user-space via
> netlink from the driver might have changed their schema, i.e. adding
> new fields in the middle of a structure or moving fields around within
> a structure.
Looks more like a crypto problem to me, as this should be the encrypted
challenge in your shared key handshake. IOW, it looks like the frame
isn't getting decrypted by mac80211 for some reason.
johannes
next prev parent reply other threads:[~2010-08-25 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 1:18 Marshaling issues w/ compat-wireless-2010-08-19 Philip Prindeville
2010-08-25 8:11 ` Johannes Berg [this message]
2010-08-25 8:20 ` Johannes Berg
2010-08-25 17:23 ` Philip Prindeville
2010-08-25 18:42 ` Philip Prindeville
2010-08-25 18:44 ` Johannes Berg
2010-08-28 17:12 ` Jouni Malinen
2010-08-28 17:19 ` Philip Prindeville
2010-08-31 1:07 ` Philip Prindeville
2010-09-03 21:52 ` Philip Prindeville
2010-09-04 8:43 ` Johannes Berg
2010-09-04 22:45 ` Philip Prindeville
2010-09-14 13:04 ` 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=1282723861.3685.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.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;
as well as URLs for NNTP newsgroup(s).