All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Andrea Rossato <mailing_list@istitutocolli.org>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	"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 10:15:23 -0700	[thread overview]
Message-ID: <20090805171523.GE4727@mosca> (raw)
In-Reply-To: <20090805165227.GA18394@eeepc.nowhere.net>

Please include linux-wireless, addint it back again.

On Wed, Aug 05, 2009 at 09:52:27AM -0700, Andrea Rossato wrote:
> On Wed, Aug 05, 2009 at 05:10:18PM +0200, Luis R. Rodriguez wrote:
> > Can you try with -D nl80211 and see if that fixes your issue?
> 
> I'll be able to try that in a couple of days... I'm now in the
> situation when I run my eee pc in Master mode.
> 
> >
> > Also from your description of the issue below it is unclear to me if
> > you do not see these issues with an older kernel or if this is only
> > happening with newer kernels or wireless-testing. Can you please
> > clarify.
> 
> 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?

> Since my scripts always call "wpa_cli reassociate" I was not aware of
> the fact that the first time wpa_supplicant was succeeding in
> associating the first time (hence the Access Point log that show the
> first successful association and nothing more).

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

ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
        ssid="mosca"
        scan_ssid=1
        key_mgmt=NONE
}

> On Wed, Aug 05, 2009 at 05:53:31PM +0200, Luis R. Rodriguez wrote:
> >
> > Also please install iw, and provide 'iw event -t' log.
> 
> Already installed here. I'll provide the output as soon as I'll be
> able to test the nl80211 driver.

May want to update from git, iw has been updated recently so you could
decode more messages specially if using wireless-testing.

  Luis

  parent reply	other threads:[~2009-08-05 17:15 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 [this message]
2009-08-05 17:31       ` Andrea Rossato
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=20090805171523.GE4727@mosca \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mailing_list@istitutocolli.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 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.