All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Jouni Malinen <j@w1.fi>,
	"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] Allow scanning while in authenticated only state
Date: Tue, 03 Nov 2009 09:16:14 +0100	[thread overview]
Message-ID: <1257236174.28469.35.camel@johannes.local> (raw)
In-Reply-To: <1257203821.6717.24.camel@maxim-laptop>

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

On Tue, 2009-11-03 at 01:17 +0200, Maxim Levitsky wrote:

> > There should be no need for doing both disassoc and deauth; just send
> > deauth only if that is needed. This will save one extra frame
> > transmission and speeds up roaming a bit.
> > 
> > Though, is this enough to handle the roaming cases where wpa_supplicant
> > may not try to send either disassociation or deauthentication?

> Currently wpa_supplicant sends only disassociation.
> deauthentication is send only in rare cases, usually due to [suspected]
> authentication error.
> Other that that I don't know, what I need is a clear statement about how
> things should work that is:
> 
> 
> * Should kernel allow authentication while in authenticated? I guess yes
> To same AP? To different APs?

It does allow it to different APs (up to 3/4 at a time), but not to the
same AP -- I plan on fixing the latter case.

> * What should kernel do if it done authentication to several APs?, but
> not association.
> should it timeout, or let wpa_suplicant do it?
> Currently it allows 4 (or 3) such APs, and then then bugs out with
> -ENOSPC

IMHO it should not make the decision on how long authentications are
valid. Any such value might be wrong if wpa_supplicant is really slow,
say it's swapped out.

> * Should kernel allow scanning while in authenticated but not associated
> case? 
> I have send patch to do so, I hope it will be accepted.

I don't think it should, and as such don't think I want to accept the
patch. You need to make a much much better case for it if you want me to
accept it. I see no reason to ever be in a situation where there are
authentications (that aren't either killed off or used to associate) for
a long enough period of time for it to make sense to scan in that time.

johannes

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

  reply	other threads:[~2009-11-03  8:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 21:49 [PATH 0/2] Make driver_nl80211 really work Maxim Levitsky
2009-10-30 21:52 ` [PATCH 1/2] Allow scanning while in authenticated only state Maxim Levitsky
2009-10-31  5:43   ` Johannes Berg
2009-10-31  9:46     ` Maxim Levitsky
2009-10-31 10:02       ` Johannes Berg
2009-10-31 10:33         ` Maxim Levitsky
2009-10-31 10:44           ` Johannes Berg
2009-11-01 20:10           ` Jouni Malinen
2009-11-02 23:17             ` Maxim Levitsky
2009-11-03  8:16               ` Johannes Berg [this message]
2009-10-30 21:54 ` [PATCH 2/2] nl80211: allow to authenticate to access point that we already authenticated Maxim Levitsky
2009-10-31  5:44   ` Johannes Berg
2009-10-31  9:36     ` Maxim Levitsky
2009-10-30 22:33 ` [PATH 0/2] Make driver_nl80211 really work Maxim Levitsky

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=1257236174.28469.35.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=hostap@lists.shmoo.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maximlevitsky@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 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.