From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Jouni Malinen <Jouni.Malinen@Atheros.com>
Subject: Re: [PATCH] [RFC] mac80211: Disable HT negotiation with TKIP/WEP as pairwise cipher
Date: Fri, 19 Dec 2008 19:55:49 +0530 [thread overview]
Message-ID: <20081219142549.GA22031@vasanth-lnx.users.atheros.com> (raw)
In-Reply-To: <1229692655.3601.74.camel@johannes.berg>
On Fri, Dec 19, 2008 at 06:47:34PM +0530, Johannes Berg wrote:
> On Fri, 2008-12-19 at 18:40 +0530, Vasanthakumar Thiagarajan wrote:
> > IEEE802.11n does not allow TKIP/WEP as pairwise cipher in HT mode.
> > Connect in non-ht mode if either of these ciphers is cofigured as
> > pairwise.
> > net/mac80211/ieee80211_i.h | 1 +
> > net/mac80211/mlme.c | 9 ++++++++-
> > net/mac80211/wext.c | 5 ++++-
> > 3 files changed, 13 insertions(+), 2 deletions(-)
>
> Needs to touch cfg.c too, I think?
I think you are referring to populating ucast_cipher in
add_key() hook in cfg.c but we need the pairwise cipher before
starting the association in HT mode.
>I'd also prefer to avoid using the
> wext constants throughout mac80211.
ok.
>
> johannes
Thanks for your comments.
Vasanth
next prev parent reply other threads:[~2008-12-19 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 13:10 [PATCH] [RFC] mac80211: Disable HT negotiation with TKIP/WEP as pairwise cipher Vasanthakumar Thiagarajan
2008-12-19 13:17 ` Johannes Berg
2008-12-19 14:25 ` Vasanthakumar Thiagarajan [this message]
2008-12-19 14:28 ` John W. Linville
2008-12-19 14:33 ` Vasanthakumar Thiagarajan
2008-12-19 14:42 ` John W. Linville
2008-12-19 14:52 ` Richard Farina
2008-12-19 14:56 ` Jouni Malinen
2008-12-19 15:30 ` John W. Linville
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=20081219142549.GA22031@vasanth-lnx.users.atheros.com \
--to=vasanth@atheros.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=Vasanth.Thiagarajan@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.