From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
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 20:03:34 +0530 [thread overview]
Message-ID: <494BB0BE.3030705@atheros.com> (raw)
In-Reply-To: <20081219142822.GA4041@tuxdriver.com>
John W. Linville wrote:
> On Fri, Dec 19, 2008 at 06:40:35PM +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.
>>
>> Signed-off-by: Vasanthakumar Thiagarajan <vasanth@atheros.com>
>
> Are there perhaps any broken APs out there that support such a
> configuration? I would hate to prevent users from connecting simply
> out of blind obedience to the standard.
This particular configuration is not allowed in the latest 11n draft (7.0).
Yes, we have quite a few AP's around which support this configuration.
Vasanth
next prev parent reply other threads:[~2008-12-19 14:35 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
2008-12-19 14:28 ` John W. Linville
2008-12-19 14:33 ` Vasanthakumar Thiagarajan [this message]
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=494BB0BE.3030705@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 \
--cc=linville@tuxdriver.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 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.