From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35741 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752960AbZBFUv2 (ORCPT ); Fri, 6 Feb 2009 15:51:28 -0500 Subject: Re: turning off IBSS (with wext) From: Dan Williams To: Johannes Berg Cc: Jouni Malinen , linux-wireless In-Reply-To: <1233952826.4175.21.camel@johannes.local> References: <1233928622.4175.9.camel@johannes.local> <1233938496.28437.10.camel@localhost> <1233952826.4175.21.camel@johannes.local> Content-Type: text/plain Date: Fri, 06 Feb 2009 15:49:57 -0500 Message-Id: <1233953398.3476.11.camel@localhost> (sfid-20090206_215133_128670_D4F7DD50) Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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