[ath9k-devel] AR5008 and Max AMSDU length

[ath9k-devel] AR5008 and Max AMSDU length

[Kucherenko Valeriy]

Hi.

I have asked this question before but have not got any answer. Is ath9k support Max AMSDU length 7935 bytes for AR5008 chip? The "iw list" command shows that this option is supported but when I enable this option in hostapd it won't start.

I have also tested this option on AR9170 chip and it work.

Thanks.

[ath9k-devel] AR5008 and Max AMSDU length

[Mihai Moldovan]

Hi Kucherenko,

 > Is ath9k support Max AMSDU length 7935 bytes for AR5008 chip? The "iw 
list" command shows that this option is supported but when I enable this 
option in hostapd it won't start.

Are you sure you're looking at the right phy device?

My AR5008 (some D-Link DWA card) doesn't support it, as iw list shows:

Max AMSDU length: 3839 bytes

Maybe someone else can help, though.

Best regards,


Mihai


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110602/5cb72e4f/attachment.bin 

[ath9k-devel] AR5008 and Max AMSDU length

[Kucherenko Valeriy]

Yes, I'm sure that this is a right phy device because currently I have only one connected - TP-Link TL-WN951N. Full "iw list" output look like:

Welcome to Ubuntu 11.04 (GNU/Linux 2.6.39-0-generic i686)
Last login: Thu Jun  2 17:49:47 2011 from 192.168.0.5
root at gateway:~# iw list
Wiphy phy0
        Band 1:
                Capabilities: 0x104e
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm)
                        * 2472 MHz [13] (20.0 dBm)
                        * 2484 MHz [14] (disabled)
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        max # scan SSIDs: 4
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * Unknown mode (8)
                 * Unknown mode (9)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * new_beacon
                 * new_station
                 * new_mpath
                 * set_mesh_params
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * Unknown command (68)
                 * Unknown command (55)
                 * Unknown command (57)
                 * Unknown command (59)
                 * Unknown command (67)
                 * set_wiphy_netns
                 * Unknown command (65)
                 * Unknown command (66)
                 * connect
                 * disconnect

--- ???????? ????????? ---
 ?? ????: "Mihai Moldovan" <ionic@ionic.de> 
 ????: ath9k-devel at lists.ath9k.org 
 ????: 2 ???? 2011, 18:21:25 
 ????: Re: [ath9k-devel] AR5008 and Max AMSDU length 
 


> Hi Kucherenko,
> 
>  > Is ath9k support Max AMSDU length 7935 bytes for AR5008 chip? The "iw 
> list" command shows that this option is supported but when I enable this 
> option in hostapd it won't start.
> 
> Are you sure you're looking at the right phy device?
> 
> My AR5008 (some D-Link DWA card) doesn't support it, as iw list shows:
> 
> Max AMSDU length: 3839 bytes
> 
> Maybe someone else can help, though.
> 
> Best regards,
> 
> 
> Mihai
> 
> 
> 
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> 
> 

[ath9k-devel] AR5008 and Max AMSDU length

[Mihai Moldovan]

* On 02.06.2011 05:36 PM, Kucherenko Valeriy wrote:
>                          Max AMSDU length: 7935 bytes

Weird, did you try the git version of hostapd?

None of my cards support this mode, so I can't test for you. :(

Best regards,


Mihai

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110602/345f84c3/attachment-0001.bin 

[ath9k-devel] AR5008 and Max AMSDU length

[Galen]

On Jun 2, 2011, at 10:24 AM, Mihai Moldovan wrote:

> * On 02.06.2011 05:36 PM, Kucherenko Valeriy wrote:
>>                         Max AMSDU length: 7935 bytes
> 
> Weird, did you try the git version of hostapd?
> 
> None of my cards support this mode, so I can't test for you. :(
> 
> Best regards,
> 
> 
> Mihai

I have also had problems with AMSDU length. Try sticking to 3839 to be on the safe side.

I would like to learn more about the physical limits in Atheros chipsets...

-Galen

[ath9k-devel] AR5008 and Max AMSDU length

[Adrian Chadd]

On 3 June 2011 02:51, Galen <galenz@zinkconsulting.com> wrote:

> I have also had problems with AMSDU length. Try sticking to 3839 to be on the safe side.
>
> I would like to learn more about the physical limits in Atheros chipsets...

.. physical limits?


Adrian

[ath9k-devel] AR5008 and Max AMSDU length

[Valeriy Kucherenko]

I'm already using last git version :)

--- ???????? ????????? ---
 ?? ????: "Mihai Moldovan" <ionic@ionic.de> 
 ????: "Kucherenko Valeriy" <darkside_ua@ukr.net> 
 ????: 2 ???? 2011, 20:24:53 
 ????: Re: [ath9k-devel] AR5008 and Max AMSDU length 
 


> * On 02.06.2011 05:36 PM, Kucherenko Valeriy wrote:
> > Max AMSDU length: 7935 bytes
> 
> Weird, did you try the git version of hostapd?
> 
> None of my cards support this mode, so I can't test for you. :(
> 
> Best regards,
> 
> 
> Mihai
> 
> 
> 

[ath9k-devel] AR5008 and Max AMSDU length

[Valeriy Kucherenko]

This is not an options. This could be a bug, so it's better to find what is this.

--- ???????? ????????? ---
 ?? ????: "Galen" <galenz@zinkconsulting.com> 
 ????: "Mihai Moldovan" <ionic@ionic.de> 
 ????: 2 ???? 2011, 21:51:47 
 ????: Re: [ath9k-devel] AR5008 and Max AMSDU length 
 


> On Jun 2, 2011, at 10:24 AM, Mihai Moldovan wrote:
> 
> > * On 02.06.2011 05:36 PM, Kucherenko Valeriy wrote:
> >> Max AMSDU length: 7935 bytes
> > 
> > Weird, did you try the git version of hostapd?
> > 
> > None of my cards support this mode, so I can't test for you. :(
> > 
> > Best regards,
> > 
> > 
> > Mihai
> 
> I have also had problems with AMSDU length. Try sticking to 3839 to be on the safe side.
> 
> I would like to learn more about the physical limits in Atheros chipsets...
> 
> -Galen
> 

[ath9k-devel] AR5008 and Max AMSDU length

[Mihai Moldovan]

* On 03.06.2011 11:36 AM, Valeriy Kucherenko wrote:
> I'm already using last git version :)

What iw version are you... actually screw that. Please get the source 
and see, whether this patch is already included in your iw version:

http://www.spinics.net/lists/linux-wireless/msg52587.html

Obviously someone confused both values in earlier versions (though this 
is pretty old, from 2010, but maybe your version is old, too.)

Interestingly, I've just learned today that exactly the same card in 
another box is capable of max AMSDU 7935, though iw list reports for me 
it isn't. Maybe there is indeed some weird bug in ath9k and for instance 
Ubuntu already patched that.

Best regards,


Mihai


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110603/890a0d0d/attachment.bin 

[ath9k-devel] AR5008 and Max AMSDU length

[Valeriy Kucherenko]

I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would be really pity if it contain drivers from compat-wireless from year 2010.

--- ???????? ????????? ---
 ?? ????: "Mihai Moldovan" <ionic@ionic.de> 
 ????: "Valeriy Kucherenko" <darkside_ua@ukr.net> 
 ????: 3 ???? 2011, 14:48:46 
 ????: Re: [ath9k-devel] AR5008 and Max AMSDU length 
 


> * On 03.06.2011 11:36 AM, Valeriy Kucherenko wrote:
> > I'm already using last git version :)
> 
> What iw version are you... actually screw that. Please get the source 
> and see, whether this patch is already included in your iw version:
> 
> http://www.spinics.net/lists/linux-wireless/msg52587.html
> 
> Obviously someone confused both values in earlier versions (though this 
> is pretty old, from 2010, but maybe your version is old, too.)
> 
> Interestingly, I've just learned today that exactly the same card in 
> another box is capable of max AMSDU 7935, though iw list reports for me 
> it isn't. Maybe there is indeed some weird bug in ath9k and for instance 
> Ubuntu already patched that.
> 
> Best regards,
> 
> 
> Mihai
> 
> 
> 
> 

[ath9k-devel] AR5008 and Max AMSDU length

[Mihai Moldovan]

* On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
> I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would be really pity if it contain drivers from compat-wireless from year 2010.

Yes, that's way too old. Please upgrade to 0.9.22.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110603/e8c57eea/attachment.bin 

[ath9k-devel] AR5008 and Max AMSDU length

[Mihai Moldovan]

* On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
> I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would be really pity if it contain drivers from compat-wireless from year 2010.

Btw, the iw tool has nothing to do with the drivers. :)

It's just versions older than 0.9.22 have a bug reporting max. AMSDU 
7935 when the card does actually not support it.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110603/b4374491/attachment-0001.bin 

[ath9k-devel] AR5008 and Max AMSDU length

[Valeriy Kucherenko]

Hm... Thanks for info.

Btw, iw tool is in compat-wireless package or it's standalone utility?

--- ???????? ????????? ---
 ?? ????: "Mihai Moldovan" <ionic@ionic.de> 
 ????: "Valeriy Kucherenko" <darkside_ua@ukr.net> 
 ????: 3 ???? 2011, 15:16:28 
 ????: Re: [ath9k-devel] AR5008 and Max AMSDU length 
 


> * On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
> > I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would be really pity if it contain drivers from compat-wireless from year 2010.
> 
> Btw, the iw tool has nothing to do with the drivers. :)
> 
> It's just versions older than 0.9.22 have a bug reporting max. AMSDU 
> 7935 when the card does actually not support it.
> 
> 
> 

[ath9k-devel] AR5008 and Max AMSDU length

[Mohammed Shafi]

2011/6/3 Valeriy Kucherenko <darkside_ua@ukr.net>:
> Hm... Thanks for info.
>
> Btw, iw tool is in compat-wireless package or it's standalone utility?

doc in http://linuxwireless.org/en/users/Documentation/iw

>
> --- ???????? ????????? ---
> ??? ????: "Mihai Moldovan" <ionic@ionic.de>
> ?????: "Valeriy Kucherenko" <darkside_ua@ukr.net>
> ?????: 3 ???? 2011, 15:16:28
> ?????: Re: [ath9k-devel] AR5008 and Max AMSDU length
>
>
>
>> * On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
>> > I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would be really pity if it contain drivers from compat-wireless from year 2010.
>>
>> Btw, the iw tool has nothing to do with the drivers. :)
>>
>> It's just versions older than 0.9.22 have a bug reporting max. AMSDU
>> 7935 when the card does actually not support it.
>>
>>
>>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi

[ath9k-devel] AR5008 and Max AMSDU length

[Mihai Moldovan]

Wireless-tools is the old api, iw the new one. Thus, its a different package. :)
-- 
Sent from my HTC Vision.

Valeriy Kucherenko <darkside_ua@ukr.net> wrote:

Hm... Thanks for info.

Btw, iw tool is in compat-wireless package or it's standalone utility?

--- ???????? ????????? ---
?? ????: "Mihai Moldovan" <ionic@ionic.de> 
????: "Valeriy Kucherenko" <darkside_ua@ukr.net> 
????: 3 ???? 2011, 15:16:28 
????: Re: [ath9k-devel] AR5008 and Max AMSDU length 



> * On 03.06.2011 02:10 PM, Valeriy Kucherenko wrote:
> > I'm using iw version 0.9.19 on Ubuntu kernel 2.6.39 from kernel PPA so it would be really pity if it contain drivers from compat-wireless from year 2010.
> 
> Btw, the iw tool has nothing to do with the drivers. :)
> 
> It's just versions older than 0.9.22 have a bug reporting max. AMSDU 
> 7935 when the card does actually not support it.
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110603/18dbd7d1/attachment.htm