Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jouni Malinen <j@w1.fi>, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: turning off IBSS (with wext)
Date: Fri, 06 Feb 2009 15:49:57 -0500	[thread overview]
Message-ID: <1233953398.3476.11.camel@localhost> (raw)
In-Reply-To: <1233952826.4175.21.camel@johannes.local>

On Fri, 2009-02-06 at 21:40 +0100, Johannes Berg wrote:
> On Fri, 2009-02-06 at 11:41 -0500, Dan Williams wrote:
> > On Fri, 2009-02-06 at 14:57 +0100, Johannes Berg wrote:
> > > Hi,
> > > 
> > > so I was testing IBSS, and found this strange behaviour:
> > > 
> > >  * wpa_supplicant (or NM?) will try to do SIWMLME(disassoc) in IBSS
> > >    mode, which seems kinda wrong. Why do we accept it? We send out a
> > >    frame and then do nothing else.
> > >  * Then I thought "iwconfig wlan1 essid off" - but that fails with
> > >    -EINVAL due to ieee80211_sta_find_ibss
> > > 
> > > It seems to me that either one of those, or both, should actually turn
> > > off beaconing.
> > 
> > Either one; the supplicant uses SIWMLME(disassoc) at various times (like
> > when leaving a BSS), and NM will sometimes set a NULL SSID when
> > deactivating the device.
> 
> Fun. Neither one actually works.

Yeah; I had to recently patch wpa_supplicant to really disassociate at
Jouni's suggestion; just telling the driver to disassoc isn't adequate
in all cases, because some drivers will just try to reassoc.  Instead,
unlocking the BSSID and setting a bogus SSID will usually actually
accomplish the disassociation in addition to the MLME disassoc...

Dan


  reply	other threads:[~2009-02-06 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 13:57 turning off IBSS (with wext) Johannes Berg
2009-02-06 16:41 ` Dan Williams
2009-02-06 20:40   ` Johannes Berg
2009-02-06 20:49     ` Dan Williams [this message]
2009-02-06 20:53       ` 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=1233953398.3476.11.camel@localhost \
    --to=dcbw@redhat.com \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --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