linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Rajkumar Manoharan <rmanoharan@atheros.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: prevent authentication on channel mismatch w/ hw conf
Date: Mon, 04 Apr 2011 20:16:43 +0200	[thread overview]
Message-ID: <1301941003.3795.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1301937866-14701-1-git-send-email-rmanoharan@atheros.com>

On Mon, 2011-04-04 at 22:54 +0530, Rajkumar Manoharan wrote:
> Do not proceed authentication if hw was already configured
> with one of the vif's channel which is differed with requesting
> channel. Not doing so is causing unneccesary dissociation.
> This issue was originaly found while testing concurrent mode
> with p2p vif.

This will break any kind of pre-authentication, no?

johannes


  reply	other threads:[~2011-04-04 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 17:24 [RFC] mac80211: prevent authentication on channel mismatch w/ hw conf Rajkumar Manoharan
2011-04-04 18:16 ` Johannes Berg [this message]
2011-04-05 15:18   ` Rajkumar Manoharan
2011-04-05 15:20     ` 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=1301941003.3795.0.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmanoharan@atheros.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).