[ath9k-devel] Problem re-associating with AP

[ath9k-devel] Problem re-associating with AP

[Amit Sood]

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,

Amit Sood



      Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/

[ath9k-devel] Problem re-associating with AP

[Luis R. Rodriguez]

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

[ath9k-devel] Problem re-associating with AP

[Amit Sood]

Hi Luis,

I'm using 'network manager' with wep enabled. I'll try to disable the encryption and test.
The problem is that in iwconfig I can see the network card associated with the AP however there is no communication. So it means card is scanning the AP but somehow I can not see layer 2 communication i.e. no arp is there.

Even I restart the network nothing happens I've to manually remove and insert the ath9k module. I've another card rt2500 and there is no problem with that card.

Should you need any logs or information to analyse then let me know.

Kind Regards,

Amit Sood






----- 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

[ath9k-devel] Problem re-associating with AP

[Luis R. Rodriguez]

On Mon, Jan 5, 2009 at 3:32 PM, Amit Sood <as22_2000@yahoo.com> wrote:
> Hi Luis,
>
> I'm using 'network manager' with wep enabled. I'll try to disable the encryption and test.
> The problem is that in iwconfig I can see the network card associated with the AP however there is no communication. So it means card is scanning the AP but somehow I can not see layer 2 communication i.e. no arp is there.

What AP do you have? And what mode are you using it ? 802.11n, 802.11g?

  Luis

[ath9k-devel] Problem re-associating with AP

[Amit Sood]

Hi Luis,

Card is running on managed mode with Linksys AP on 802.11g mode.

cheers,

-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 10:48:21 AM
Subject: Re: [ath9k-devel] Problem re-associating with AP

On Mon, Jan 5, 2009 at 3:32 PM, Amit Sood <as22_2000@yahoo.com> wrote:
> Hi Luis,
>
> I'm using 'network manager' with wep enabled. I'll try to disable the encryption and test.
> The problem is that in iwconfig I can see the network card associated with the AP however there is no communication. So it means card is scanning the AP but somehow I can not see layer 2 communication i.e. no arp is there.

What AP do you have? And what mode are you using it ? 802.11n, 802.11g?

  Luis



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

[ath9k-devel] Problem re-associating with AP

[Luis R. Rodriguez]

On Tue, Jan 06, 2009 at 03:43:36AM -0800, Amit Sood wrote:
> Hi Luis,
> 
> Card is running on managed mode with Linksys AP on 802.11g mode.

What specific model AP do you have?

  Luis

[ath9k-devel] Problem re-associating with AP

[Luis R. Rodriguez]

On Tue, Jan 6, 2009 at 4:55 AM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Tue, Jan 06, 2009 at 03:43:36AM -0800, Amit Sood wrote:
>> Hi Luis,
>>
>> Card is running on managed mode with Linksys AP on 802.11g mode.

Keep in mind Network manager will give up after 7 seconds if the AP
doesn't come up and the supplicant hasn't been able to reassoc so its
up to the supplicant during those 7 seconds. If your AP reboot takes
longer than you are forced to try to reassoc. Can you try disabling
network manger and running wpa_supplicant manually and adding
ap_scan=1 ?

  Luis

[ath9k-devel] Problem re-associating with AP

[Amit Sood]

Hi Luis,

I can try that. However this problem is only with n card only.. I've another linksys card 802.11g and there is no problem.

cheers,

-amit-



----- Original Message ----
From: Luis R. Rodriguez <mcgrof@gmail.com>
To: Amit Sood <as22_2000@yahoo.com>
Cc: Luis R. Rodriguez <mcgrof@gmail.com>; "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Sent: Wednesday, 7 January, 2009 12:59:47 AM
Subject: Re: [ath9k-devel] Problem re-associating with AP

On Tue, Jan 6, 2009 at 4:55 AM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Tue, Jan 06, 2009 at 03:43:36AM -0800, Amit Sood wrote:
>> Hi Luis,
>>
>> Card is running on managed mode with Linksys AP on 802.11g mode.

Keep in mind Network manager will give up after 7 seconds if the AP
doesn't come up and the supplicant hasn't been able to reassoc so its
up to the supplicant during those 7 seconds. If your AP reboot takes
longer than you are forced to try to reassoc. Can you try disabling
network manger and running wpa_supplicant manually and adding
ap_scan=1 ?

  Luis



      Get your own website and domain for just Rs.1,999/year.* Go to http://in.business.yahoo.com/

[ath9k-devel] Problem re-associating with AP

[Amit Sood]

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

[ath9k-devel] Problem re-associating with AP

[Luis R. Rodriguez]

On Mon, Jan 19, 2009 at 09:33:57PM -0800, Amit Sood wrote:
> 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,

Are you trying WEP with 802.11n?

  Luis