Juniper MX200/MP432 802.11n running at 54Mbps

[marty]

Hello everybody

Please can you help me?

I have recently updated Juniper (formerly Trapeze) Mobility Software and Ringmaster to 9.0 and replaced by 802.11g APs with 802.11n.

FYI it's an MX200 with MP-432 APs.

I assumed 802.11n devices would automatically connect at speeds above 54Mbps (especially being in the same room as the AP) yet a whole range of modern devices only connect at 54Mbps max.

The devices include Win8 laptops and tablets, iPads and a Macbook Pro.

Is there any way I can allow faster connectivity to 802.11n devices or is it limited for a specific reason on purpose?

Thanks in advance

Marty

[SYNACK]

What encryption are you running, are you are using WPA with TKIP encryption instead of AES, AES is hardware accelerated where as tkip is in software so slower. Edited August 23, 2013 by SYNACK

[SYNACK]

Oh and tkip is also easily crackable and not in the official WPA2 spec so it behaves like 11g. Edited August 23, 2013 by SYNACK

[CyberNerd]

What encryption are you running, are you are using WPA with TKIP encryption instead of AES, AES is hardware accelerated where as tkip is in software so slower.

 

Your right, but for the wrong reason. WPA/TKIP isn't in the 802.11n specification so if the spec is being implemented properly it should default to 54Mb if WPA is being used. I'm not sure that all vendors stick religiously to the spec.

[marty]

Introducing AES encryption has fixed the issue for me.

Thanks everybody especially SYNACK for getting in first!

[SYNACK]

Your right, but for the wrong reason. WPA/TKIP isn't in the 802.11n specification so if the spec is being implemented properly it should default to 54Mb if WPA is being used. I'm not sure that all vendors stick religiously to the spec.

 

Pfft, I'm right, I need no reason . By rights the config should not even let you select tkip with n without a warning but none seem to. Our ruckus gear will let you specify wpa2 tkip on 11n but steps the speed down, in that case the number of clients is limited much lower per wap because tkip is in software where as aes is hardware accelerated and so more clients at a higher speed. In our case at least I was right on that front to which relates back to the spec. TBH I think wpa disallowed tkip even in g but venders left it in for compatibility.

Edited August 23, 2013 by SYNACK