On Sat, May 28, 2011 at 7:06 PM, Mohammed Shafi <shafi.at...@gmail.com> wrote:
> On Fri, May 27, 2011 at 8:42 PM, Bastien Nocera <had...@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@lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to