From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amit Sood Date: Tue, 20 Jan 2009 11:03:57 +0530 (IST) Subject: [ath9k-devel] Problem re-associating with AP References: <370159.70599.qm@web95013.mail.in2.yahoo.com> <43e72e890901050831o800f915m3c7728128f7dab40@mail.gmail.com> Message-ID: <75730.14487.qm@web95006.mail.in2.yahoo.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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 To: Amit Sood 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 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