From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Sujith <Sujith.Manoharan@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Fix IBSS merge
Date: Mon, 02 Nov 2009 21:27:12 +0100 [thread overview]
Message-ID: <4AEF40A0.2030408@openwrt.org> (raw)
In-Reply-To: <43e72e890911020947i3a9ea736ve95fa6b1fac724a4@mail.gmail.com>
Luis R. Rodriguez wrote:
> On Mon, Nov 2, 2009 at 9:20 AM, Felix Fietkau <nbd@nbd.name> wrote:
>> John W. Linville wrote:
>>> On Mon, Nov 02, 2009 at 09:44:46AM +0100, Johannes Berg wrote:
>>>> On Mon, 2009-11-02 at 12:33 +0530, Sujith wrote:
>>>> > Currently, in IBSS mode, a single creator would go into
>>>> > a loop trying to merge/scan. This happens because the IBSS timer is
>>>> > rearmed on finishing a scan and the subsequent
>>>> > timer invocation requests another scan immediately.
>>>> >
>>>> > This patch fixes this issue by checking if we have just completed
>>>> > a scan run trying to merge with other IBSS networks.
>>>>
>>>> Heh, how many people do we need to fix IBSS? :)
>>>
>>> Yeah, no kidding...I suspect that actual IBSS users are few, and a
>>> substantial number of those are doing crazy things with it! :-)
>> Yeah, we're doing crazy things like mesh networks of few hundred
>> nodes... something that 11s isn't really suitable for. :-)
>
> Anyone know if this applies for 32?
What exactly?
- Felix
next prev parent reply other threads:[~2009-11-02 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 7:03 [PATCH] mac80211: Fix IBSS merge Sujith
2009-11-02 8:44 ` Johannes Berg
2009-11-02 9:18 ` Sujith
2009-11-02 9:39 ` Johannes Berg
2009-11-02 15:36 ` John W. Linville
2009-11-02 17:20 ` Felix Fietkau
2009-11-02 17:47 ` Luis R. Rodriguez
2009-11-02 20:27 ` Felix Fietkau [this message]
2009-11-02 20:36 ` Luis R. Rodriguez
2009-11-02 20:43 ` John W. Linville
2009-11-02 18:32 ` John W. Linville
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=4AEF40A0.2030408@openwrt.org \
--to=nbd@openwrt.org \
--cc=Sujith.Manoharan@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@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 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).