[ath9k-devel] Problems using WeTab's ath9k after AP association

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Bastien Nocera]

Heya,

I'm having problems using the ath9k in a recently purchased WeTab. All the other
devices in my home have no problems connecting to the wireless (offered by a
 DD-WRT AP running on a DIR-315 router).

The problems occur after the device finds the network, associates with it, and 
gets a DHCP lease. The device then cannot ping the AP, and absolutely no
 traffic comes in or out of the tablet.

I'm lead to believe that the problem is due to regulatory domains. My AP works
 in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
 have DE as the domain burnt into the EEPROM.

I have some semblance of a bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=701768
but John Linville didn't know the specifics to help me out.

Anybody with hints as to what I should be trying? I'm more than happy changing
 the wireless configuration of the AP, if it can give me working Wi-Fi, but I 
would certainly like to understand what the problem is.

Cheers

PS: Please CC: me as I'm not on the list.

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Mohammed Shafi]

On Sat, May 21, 2011 at 1:04 AM, Bastien Nocera <hadess@hadess.net> wrote:
> Heya,
>
> I'm having problems using the ath9k in a recently purchased WeTab. All the other
> devices in my home have no problems connecting to the wireless (offered by a
> ?DD-WRT AP running on a DIR-315 router).
>
> The problems occur after the device finds the network, associates with it, and
> gets a DHCP lease. The device then cannot ping the AP, and absolutely no
> ?traffic comes in or out of the tablet.

does the monitor mode works ? or please try to use to receive traffic
from the device (iperf  -s -i 1)
how about disabling the security and see if its working

>
> I'm lead to believe that the problem is due to regulatory domains. My AP works
> ?in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
> ?have DE as the domain burnt into the EEPROM.

very very less idea about regulatory

>
> I have some semblance of a bug report here:
> https://bugzilla.redhat.com/show_bug.cgi?id=701768
> but John Linville didn't know the specifics to help me out.

is it possible for you to try with compat wireless though you have 2.6.39*
http://linuxwireless.org/download/compat-wireless-2.6/

also can you post debug information by enabling ath9k debug sudo
modprobe ath9k debug=0x482
http://linuxwireless.org/en/users/Drivers/ath9k/debug
>
> Anybody with hints as to what I should be trying? I'm more than happy changing
> ?the wireless configuration of the AP, if it can give me working Wi-Fi, but I
> would certainly like to understand what the problem is.
>
> Cheers
>
> PS: Please CC: me as I'm not on the list.
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Bastien Nocera]

Mohammed Shafi <shafi.ath9k <at> gmail.com> writes:
> does the monitor mode works ? or please try to use to receive traffic
> from the device (iperf  -s -i 1)
> how about disabling the security and see if its working

Disabling security didn't change anything. Tested with various combinations of 
WPA2 Personal, WPA Personal, and even disabling the security, and didn't change 
the status.

> > I'm lead to believe that the problem is due to regulatory domains. My AP 
works
> > ?in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
> > ?have DE as the domain burnt into the EEPROM.
> 
> very very less idea about regulatory

I managed to make it work by switching from 40MHz channel width (for an 
advertised speed of 300Mb/s) to a 20MHz channel width (144Mb/s).

I'm not certain whether the problem is a regulatory one, or not.

The dmesg output only seemed to contain useless statements. Not sure if debug is 
disabled somewhat on those devices. I'll probably switch my network to 20MHz 
channel width, while trying to work out why 40MHz doesn't.

Cheers

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Mohammed Shafi]

On Fri, May 27, 2011 at 8:42 PM, Bastien Nocera <hadess@hadess.net> wrote:
> Mohammed Shafi <shafi.ath9k <at> gmail.com> writes:
>> does the monitor mode works ? or please try to use to receive traffic
>> from the device (iperf ?-s -i 1)
>> how about disabling the security and see if its working
>
> Disabling security didn't change anything. Tested with various combinations of
> WPA2 Personal, WPA Personal, and even disabling the security, and didn't change
> the status.

thanks for testing it.

>
>> > I'm lead to believe that the problem is due to regulatory domains. My AP
> works
>> > ?in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
>> > ?have DE as the domain burnt into the EEPROM.
>>
>> very very less idea about regulatory
>
> I managed to make it work by switching from 40MHz channel width (for an
> advertised speed of 300Mb/s) to a 20MHz channel width (144Mb/s).
>
> I'm not certain whether the problem is a regulatory one, or not.
>
> The dmesg output only seemed to contain useless statements. Not sure if debug is
> disabled somewhat on those devices. I'll probably switch my network to 20MHz
> channel width, while trying to work out why 40MHz doesn't.

great finding! please let us know the card.
lspci -vvvxxx

I will test the card by configuring the AP in static 40Mhz and try to
see the traffic goes on. we found one similar issue for htc
http://www.spinics.net/lists/linux-wireless/msg66161.html

if you use compat wireless/ wireless testing the debug messages might
help, please post them
http://linuxwireless.org/en/users/Drivers/ath9k/debug

>
> Cheers
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Mohammed Shafi]

On Sat, May 28, 2011 at 5:40 PM, Mohammed Shafi <shafi.ath9k@gmail.com> wrote:
> On Fri, May 27, 2011 at 8:42 PM, Bastien Nocera <hadess@hadess.net> wrote:
>> Mohammed Shafi <shafi.ath9k <at> gmail.com> writes:
>>> does the monitor mode works ? or please try to use to receive traffic
>>> from the device (iperf ?-s -i 1)
>>> how about disabling the security and see if its working
>>
>> Disabling security didn't change anything. Tested with various combinations of
>> WPA2 Personal, WPA Personal, and even disabling the security, and didn't change
>> the status.
>
> thanks for testing it.
>
>>
>>> > I'm lead to believe that the problem is due to regulatory domains. My AP
>> works
>>> > ?in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
>>> > ?have DE as the domain burnt into the EEPROM.
>>>
>>> very very less idea about regulatory
>>
>> I managed to make it work by switching from 40MHz channel width (for an
>> advertised speed of 300Mb/s) to a 20MHz channel width (144Mb/s).
>>
>> I'm not certain whether the problem is a regulatory one, or not.
>>
>> The dmesg output only seemed to contain useless statements. Not sure if debug is
>> disabled somewhat on those devices. I'll probably switch my network to 20MHz
>> channel width, while trying to work out why 40MHz doesn't.
>
> great finding! please let us know the card.
> lspci -vvvxxx

AR9285 found in the dmesg you had posted in the bugzilla.. let me try

>
> I will test the card by configuring the AP in static 40Mhz and try to
> see the traffic goes on. we found one similar issue for htc
> http://www.spinics.net/lists/linux-wireless/msg66161.html
>
> if you use compat wireless/ wireless testing the debug messages might
> help, please post them
> http://linuxwireless.org/en/users/Drivers/ath9k/debug
>
>>
>> Cheers
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Mohammed Shafi]

On Fri, May 27, 2011 at 8:42 PM, Bastien Nocera <hadess@hadess.net> wrote:
> Mohammed Shafi <shafi.ath9k <at> gmail.com> writes:
>> does the monitor mode works ? or please try to use to receive traffic
>> from the device (iperf ?-s -i 1)
>> how about disabling the security and see if its working
>
> Disabling security didn't change anything. Tested with various combinations of
> WPA2 Personal, WPA Personal, and even disabling the security, and didn't change
> the status.
>
>> > I'm lead to believe that the problem is due to regulatory domains. My AP
> works
>> > ?in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
>> > ?have DE as the domain burnt into the EEPROM.
>>
>> very very less idea about regulatory
>
> I managed to make it work by switching from 40MHz channel width (for an
> advertised speed of 300Mb/s) to a 20MHz channel width (144Mb/s).

in your dmesg
Strength 17 WPA WPA2
    *idoru:          Infra, 1C:AF:F7:45:94:CE, Freq 2457 MHz, Rate 54 Mb/s,
any reason for being in  channel 10, possible to change to 1,6 or 11?

>
> I'm not certain whether the problem is a regulatory one, or not.
>
> The dmesg output only seemed to contain useless statements. Not sure if debug is
> disabled somewhat on those devices. I'll probably switch my network to 20MHz
> channel width, while trying to work out why 40MHz doesn't.
>
> Cheers
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Mohammed Shafi]

On Sat, May 28, 2011 at 7:06 PM, Mohammed Shafi <shafi.ath9k@gmail.com> wrote:
> On Fri, May 27, 2011 at 8:42 PM, Bastien Nocera <hadess@hadess.net> wrote:
>> Mohammed Shafi <shafi.ath9k <at> gmail.com> writes:
>>> does the monitor mode works ? or please try to use to receive traffic
>>> from the device (iperf ?-s -i 1)
>>> how about disabling the security and see if its working
>>
>> Disabling security didn't change anything. Tested with various combinations of
>> WPA2 Personal, WPA Personal, and even disabling the security, and didn't change
>> the status.
>>
>>> > I'm lead to believe that the problem is due to regulatory domains. My AP
>> works
>>> > ?in the 2.4GHz range, in the GB regulatory domain whereas the device seems to
>>> > ?have DE as the domain burnt into the EEPROM.
>>>
>>> very very less idea about regulatory
>>
>> I managed to make it work by switching from 40MHz channel width (for an
>> advertised speed of 300Mb/s) to a 20MHz channel width (144Mb/s).
>
> in your dmesg
> Strength 17 WPA WPA2
> ? ?*idoru: ? ? ? ? ?Infra, 1C:AF:F7:45:94:CE, Freq 2457 MHz, Rate 54 Mb/s,
> any reason for being in ?channel 10, possible to change to 1,6 or 11?

surely the channel thing looks suspicious channel 1/6 in HT40  may
help I think.. please try

>
>>
>> I'm not certain whether the problem is a regulatory one, or not.
>>
>> The dmesg output only seemed to contain useless statements. Not sure if debug is
>> disabled somewhat on those devices. I'll probably switch my network to 20MHz
>> channel width, while trying to work out why 40MHz doesn't.
>>
>> Cheers
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>

[ath9k-devel] Problems using WeTab's ath9k after AP association

[Bastien Nocera]

Mohammed Shafi <shafi.ath9k <at> gmail.com> writes:
> On Sat, May 28, 2011 at 7:06 PM, Mohammed Shafi <shafi.ath9k <at> gmail.com> 
wrote:
<snip>
> > in your dmesg
> > Strength 17 WPA WPA2
> > ? ?*idoru: ? ? ? ? ?Infra, 1C:AF:F7:45:94:CE, Freq 2457 MHz, Rate 54 Mb/s,
> > any reason for being in ?channel 10, possible to change to 1,6 or 11?
> 
> surely the channel thing looks suspicious channel 1/6 in HT40  may
> help I think.. please try

- Switched to channel 1 in 40MHz (lower channel for control), working.
- Tried with 6, no dice (tried both upper and lower channels as control channel).
- Trying with 11 (upper control channel), works.

Any ideas why all my other Wi-Fi devices can handle channel 10/40 MHz and not 
this one?