From: Ignacy Gawedzki <i@lri.fr>
To: linux-wireless@vger.kernel.org
Subject: Re: sta_find_ibss (active_ibss=1) in a loop?
Date: Fri, 3 Jun 2011 22:49:39 +0200 [thread overview]
Message-ID: <20110603204939.GA12854@zenon.in.qult.net> (raw)
In-Reply-To: <20110603201644.GA7836@zenon.in.qult.net>
On Fri, Jun 03, 2011 at 10:16:44PM +0200, thus spake Ignacy Gawedzki:
> I can't confirm right now that this is indeed what's happening, but I'll post
> more information as soon as possible.
I can now confirm that the state is MLME_SEARCH and that the ignored station
can't be added because of the following in ieee80211_ibss_add_sta():
if (ifibss->state == IEEE80211_IBSS_MLME_SEARCH)
return NULL;
--
I have not lost my mind, it's backed up on disk somewhere.
next prev parent reply other threads:[~2011-06-03 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 20:16 sta_find_ibss (active_ibss=1) in a loop? Ignacy Gawedzki
2011-06-03 20:49 ` Ignacy Gawedzki [this message]
2011-06-06 11:04 ` Ignacy Gawedzki
2011-06-06 14:31 ` Johannes Berg
2011-06-06 16:01 ` Ignacy Gawedzki
2011-06-06 16:11 ` Johannes Berg
2011-06-08 11:13 ` Ignacy Gawedzki
2011-06-08 11:26 ` 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=20110603204939.GA12854@zenon.in.qult.net \
--to=i@lri.fr \
--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).