Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Jouni Malinen <j@w1.fi>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: mac80211 ad-hoc mode problems
Date: Wed, 04 Jun 2008 13:30:32 -0400	[thread overview]
Message-ID: <1212600632.20764.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20080604155504.GH580@jm.kir.nu>

On Wed, 2008-06-04 at 18:55 +0300, Jouni Malinen wrote:
> On Wed, Jun 04, 2008 at 10:18:24AM -0400, Dan Williams wrote:
> 
> > 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?
> 
> As long as there is still enough time for the scan to be completed
> before deciding to create a new IBSS. I don't remember how that code
> worked, so I don't know whether 5 second as the IBSS timeout will
> guarantee this for every case. If there are any problems in providing
> such guarantee, I have nothing against increasing the wpa_supplicant
> timeout for IBSS. I might do that anyway since there is not really much
> point in timing out IBSS join/create in most cases.

That's probably the best solution; to increase the supplicant's timeout
for the IBSS case and decrease the mac80211 IBSS create timeout.

Dan


  reply	other threads:[~2008-06-04 17:30 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
2008-06-04 15:55       ` Jouni Malinen
2008-06-04 17:30         ` Dan Williams [this message]
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=1212600632.20764.7.camel@localhost.localdomain \
    --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