linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Tim Gardner <tim.gardner@canonical.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] Fix NetworkManager/wpa_supplicant race condition
Date: Thu, 19 Apr 2007 09:51:07 -0600	[thread overview]
Message-ID: <46278FEB.50203@canonical.com> (raw)
In-Reply-To: <1176951852.3207.1.camel@localhost.localdomain>

Dan Williams wrote:

snip, snip

> 
> When I say "reassociate", I mean a new association cycle to the _same_
> BSSID/SSID using the settings that are current at that point in time.  I
> guess I should have made that clear.
> 
> Dan
> 
>> A quick look at ieee80211_ioctl_siwessid() shows that it always forces
>> an authentication cycle.
>>
>> I'll experiment a little to see how the Softmac can be driven through an
>> authentication/association cycle on calls to SIOCSIWESSID or SIOCSIWAP.
>>
>> rtg

Dan,

I agree that driving the SoftMAC protocol through an auth/assoc cycle
when changing ESSID or BSSID is architecturally the right thing to do.
However, the required changes are a bit too extensive for me to add to a
recently released kernel (Feisty).  I'll have to get back to this when I
have more freedom to whack and slash.

In the meantime, I still think emitting an ASSOC event is a good interim
fix. I'll be testing it over the next few days within the Ubuntu community.

rtg
-- 
Tim Gardner tim.gardner@ubuntu.com

      reply	other threads:[~2007-04-19 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18 16:40 [PATCH] Fix NetworkManager/wpa_supplicant race condition Tim Gardner
2007-04-18 17:22 ` Dan Williams
2007-04-18 19:18   ` Tim Gardner
2007-04-19  3:04     ` Dan Williams
2007-04-19 15:51       ` Tim Gardner [this message]

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=46278FEB.50203@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=dcbw@redhat.com \
    --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 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).