From: Johannes Berg <johannes@sipsolutions.net>
To: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Cc: linux-wireless@vger.kernel.org, Javier Cardona <javier@cozybit.com>
Subject: Re: Hw Accel in Secured Mesh No Longer Work
Date: Wed, 07 Mar 2012 15:31:26 +0100 [thread overview]
Message-ID: <1331130686.3519.14.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAEFj984tNRXvBL4cCdJAq2VL7_AgeFYDB=w1b=aLy89pCM5UdA@mail.gmail.com> (sfid-20120307_152224_978018_6FCBF45E)
Hi,
> > Huh? Well that's odd, maybe there's a race condition and you program the
> > key before the peer was added to the device?
>
> Not so sure. The adding of key is actually done by the meshd-nl80211
> (authsae) daemon running in userspace.
>
> https://github.com/cozybit/authsae/blob/master/linux/meshd-nl80211.c
>
> /* key to encrypt/decrypt unicast data AND mgmt traffic to/from this peer */
> install_key(&nlcfg, peer, CIPHER_CCMP, NL80211_KEYTYPE_PAIRWISE, 0, mtk);
Yeah but that always required a station ... now you have a station but
it's not uploaded.
> > What device are you working with?
> I am using atheros 11n chipset (ath9k).
Ok.
I think you're probably trying to set a key before the station is set to
associated?
johannes
next prev parent reply other threads:[~2012-03-07 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEFj984b_Aihd9hc-dMArPxZPod8eKsxzekLwO74XbTUKGX9LQ@mail.gmail.com>
[not found] ` <CAEFj984gKDRtjP9NJYqjvWCZ=HxwW3DQ036guVY6Vbj=yx1H6g@mail.gmail.com>
2012-03-07 7:38 ` Hw Accel in Secured Mesh No Longer Work Johannes Berg
[not found] ` <CAEFj985EYVeAYef1-G3uVPOxZqwjose9Ge7=MRsbmFWrLNz_RQ@mail.gmail.com>
2012-03-07 14:21 ` Yeoh Chun-Yeow
2012-03-07 14:31 ` Johannes Berg [this message]
2012-03-07 14:33 ` Johannes Berg
2012-03-07 14:47 ` Yeoh Chun-Yeow
2012-03-07 14:50 ` Johannes Berg
2012-03-07 15:29 ` Yeoh Chun-Yeow
2012-03-07 16:07 ` Yeoh Chun-Yeow
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=1331130686.3519.14.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yeohchunyeow@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;
as well as URLs for NNTP newsgroup(s).