linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Jouni Malinen <j@w1.fi>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Tomas Winkler <tomasw@gmail.com>
Subject: Re: 11n + wpa_supplicant
Date: Tue, 13 May 2008 11:17:28 +0200	[thread overview]
Message-ID: <1210670248.3646.54.camel@johannes.berg> (raw)
In-Reply-To: <8704f27d0805130148t57a1dad5nf5ff535ae4ddf968@mail.gmail.com> (sfid-20080513_104857_603495_7A3A4A22)

[-- Attachment #1: Type: text/plain, Size: 448 bytes --]


> >  Ah, so you mean if the user chose TKIP then we should associate as a
> >  legacy STA?
> >
> 
> I think so... If the AP is N-only we would be in trouble...

Hm. I don't really see much reason to do this. Technically, you could
configure it this way, but in practice most people will just enable all
algorithms they can support (i.e. all).

I don't really care, but I wouldn't want to complicate wext further for
this.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-05-13  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  8:18 11n + wpa_supplicant Emmanuel Grumbach
2008-05-13  8:28 ` Johannes Berg
2008-05-13  8:41   ` Emmanuel Grumbach
2008-05-13  8:47     ` Johannes Berg
2008-05-13  8:48       ` Emmanuel Grumbach
2008-05-13  9:17         ` Johannes Berg [this message]
2008-05-13 12:30           ` John W. Linville
2008-05-13 12:30     ` Jouni Malinen
2008-05-13 12:27 ` Jouni Malinen
2008-05-13 12:34   ` Johannes Berg
2008-05-13 12:50     ` Jouni Malinen
2008-05-13 13:03       ` Emmanuel Grumbach
2008-05-13 13:10         ` Jouni Malinen
2008-05-13 14:07           ` Emmanuel Grumbach

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=1210670248.3646.54.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=egrumbach@gmail.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@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).