All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Sood <as22_2000@yahoo.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Problem re-associating with AP
Date: Tue, 20 Jan 2009 11:03:57 +0530 (IST)	[thread overview]
Message-ID: <75730.14487.qm@web95006.mail.in2.yahoo.com> (raw)
In-Reply-To: 43e72e890901050831o800f915m3c7728128f7dab40@mail.gmail.com

Hi Luis,

I tested it with wpa_supplicant but no improvement. However I noticed that the problem goes away if I uses WPA instead of WEP. So not sure what could be the reason. I tested with 3 linksys routers with same results.

Kind Regards,

-amit-



----- Original Message ----
From: Luis R. Rodriguez <mcgrof@gmail.com>
To: Amit Sood <as22_2000@yahoo.com>
Cc: ath9k-devel at lists.ath9k.org
Sent: Tuesday, 6 January, 2009 3:31:46 AM
Subject: Re: [ath9k-devel] Problem re-associating with AP

On Sat, Jan 3, 2009 at 9:18 PM, Amit Sood <as22_2000@yahoo.com> wrote:
> Hi,
>
> I'm using the latest compat wireless drivers for AR5416 chipset card (linksys). I've noticed that if wireless connectivity goes down it does not automatically comes up. I've to remove the module and modprobe the driver again. Specially if I reboot the AP. Any suggestions?
>
> Currently I've put a cron script to ping the AP and if it fails do rmmod and then modprobe ath9k.
>
> Kind Regards,

Are you using wpa_supplicant? Are you using Network Manager? Note that
wpa_supplicant would be required to force reassociation, and I believe
the option to roam is ap_scan=1, so try that, even if you are
associated to an AP without encryption..

  Luis



      Get perfect Email ID for your Resume. Grab now http://in.promos.yahoo.com/address

  parent reply	other threads:[~2009-01-20  5:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04  5:18 [ath9k-devel] Problem re-associating with AP Amit Sood
2009-01-05 16:31 ` Luis R. Rodriguez
2009-01-05 23:32   ` Amit Sood
2009-01-05 23:48     ` Luis R. Rodriguez
2009-01-06 11:43       ` Amit Sood
2009-01-06 12:55         ` Luis R. Rodriguez
2009-01-06 13:59           ` Luis R. Rodriguez
2009-01-07  4:07             ` Amit Sood
2009-01-20  5:33   ` Amit Sood [this message]
2009-01-20 18:08     ` Luis R. Rodriguez

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=75730.14487.qm@web95006.mail.in2.yahoo.com \
    --to=as22_2000@yahoo.com \
    --cc=ath9k-devel@lists.ath9k.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.