From: Johannes Berg <johannes@sipsolutions.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Jouni Malinen <j@w1.fi>, linux-wireless@vger.kernel.org
Subject: Re: mac80211 ad-hoc mode problems
Date: Wed, 04 Jun 2008 17:41:45 +0200 [thread overview]
Message-ID: <1212594106.14371.32.camel@johannes.berg> (raw)
In-Reply-To: <1212589104.13676.17.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
> > Can't remember.. The only thing I can come up with is that 20 was the
> > next round number that is larger than IEEE80211_SCAN_INTERVAL_SLOW
> > defined on the previous line.. ;-) Anyway, I don't see why we would need
> > to wait that long. It should be enough to wait for a full scan of all
> > channels to be completed. It is of course nicer to avoid creating a new
> > IBSS if there is an existing one, but as long as merging works, it
> > should be fine to reduce this timeout.
>
> Ok, I'll drop it down to 5 seconds if that's OK with you. That's still
> the same amount of time as the wpa_supplicant assoc_failed auth timeout
> in wpa_supplicant_associate() though, so they could still step on each
> other. Not quite sure what to do about that except bump up the
> wpa_supplicant assoc_failed timeout by a few more seconds?
Fine with me either way. Like I said, I don't really care too much about
IBSS and appreciate the time you're investing to make it work.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-06-04 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 1:41 mac80211 ad-hoc mode problems Dan Williams
2008-06-04 9:00 ` Johannes Berg
2008-06-04 9:16 ` Jouni Malinen
2008-06-04 14:18 ` Dan Williams
2008-06-04 15:41 ` Johannes Berg [this message]
2008-06-04 15:55 ` Jouni Malinen
2008-06-04 17:30 ` Dan Williams
2008-06-04 14:13 ` Dan Williams
2008-06-04 15:44 ` 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=1212594106.14371.32.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=j@w1.fi \
--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