All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Rossato <mailing_list@istitutocolli.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "ath5k-devel@venema.h4ckr.net" <ath5k-devel@venema.h4ckr.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] a possible regression in managed mode ?
Date: Wed, 5 Aug 2009 19:31:32 +0200	[thread overview]
Message-ID: <20090805173129.GD18549@eeepc.nowhere.net> (raw)
In-Reply-To: <20090805171523.GE4727@mosca>

On Wed, Aug 05, 2009 at 10:15:23AM -0700, Luis R. Rodriguez wrote:
> > When I use 2.6.29.4 everything works smoothly and association and
> > authentication always happen at the first try. The "authentication
> > timeout" issue only happens with the wireless-testing kernel from git.
> 
> This is when using wpa_supplicant 0.6.9? Or when using both 0.6.9
> and git version of the supplicant?

That happens with both versions.

> You know you can just have wpa_supplicant try to reassoc for you
> upon disconnection automatically, right? I use something like this:

yes, but in my setup I need to force a reassociation in order to run
the dhclient and the correct configuration script - but not at boot
time.

Thanks

Andrea

  reply	other threads:[~2009-08-05 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 15:10 [ath5k-devel] a possible regression in managed mode ? Luis R. Rodriguez
2009-08-05 15:53 ` Luis R. Rodriguez
     [not found]   ` <20090805165227.GA18394@eeepc.nowhere.net>
2009-08-05 17:15     ` Luis R. Rodriguez
2009-08-05 17:31       ` Andrea Rossato [this message]
2009-08-06 11:47   ` Andrea Rossato

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=20090805173129.GD18549@eeepc.nowhere.net \
    --to=mailing_list@istitutocolli.org \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.