.342 Firmware and PS3 Wireless

[neoshi]

Just got the N56U and it seems that the N56U doesn't like to play nice with my wireless PS3s. A quick google search shows that this has been around for a little while, maybe from .318 or so. The PS3s will see the network with 100% signal quality, but the handshake will fail.

At this point, everytime I turn on my PS3s, I have to log into the router and switch b/g protection on and off. The PS3s will then have successful handshakes. Woof.

I know many will say just use Padavan's firmware, but I wanted to know if anyone has found a way to make PS3s work wireless without this hassle on the stock firmware. Also, it is not possible to hardwire these PS3s, as they are on different floors of the house.

2.4 wifi is set on auto (instead of N only and legacy), 40Mhz, b/g protection off, WPA2-AES.

 

[RogerSC]

Just got the N56U and it seems that the N56U doesn't like to play nice with my wireless PS3s. A quick google search shows that this has been around for a little while, maybe from .318 or so. The PS3s will see the network with 100% signal quality, but the handshake will fail.

At this point, everytime I turn on my PS3s, I have to log into the router and switch b/g protection on and off. The PS3s will then have successful handshakes. Woof.

I know many will say just use Padavan's firmware, but I wanted to know if anyone has found a way to make PS3s work wireless without this hassle on the stock firmware. Also, it is not possible to hardwire these PS3s, as they are on different floors of the house.

2.4 wifi is set on auto (instead of N only and legacy), 40Mhz, b/g protection off, WPA2-AES.

I'd suggest using "20MHz. only" channel width, not 20/40 or 40MHz. Also, use something like inSSIDer to pick the best (least-used) 2.4GHz. channel for your area, don't use auto. Concentrate on channels 1, 6, and 11 in the US.

The above may or may not help, I don't have a PS3, so I don't know, but they are the recommended settings for this router.

 

[neoshi]

Hmm those settings seem to be working well. I guess it's the 20Mhz channel width that made the difference. Thanks Roger.

Edit: NVM, the problem is back. Oy. Wondering if there's a problem using WPA2-AES... I really don't want to use anything else...

 

[neoshi]

Ok, I'm confirming that this is definitely a problem with ASUS stock firmware .342, as the logs show key length errors that prevent the successful handshake. I think there's something wrong in ASUS' coding that prevents successful WPA2-AES use. Anyhow, Padavan's fw fixes it. Compromise is less TX power, so N signal strength drops massively as you walk away.

 

[RogerSC]

Ok, I'm confirming that this is definitely a problem with ASUS stock firmware .342, as the logs show key length errors that prevent the successful handshake. I think there's something wrong in ASUS' coding that prevents successful WPA2-AES use. Anyhow, Padavan's fw fixes it. Compromise is less TX power, so N signal strength drops massively as you walk away.

I did try the latest Padavan firmware yesterday as well, and agree with you. The Asus stock firmware has stronger wireless signal strength than Padavan, especially on 5.0GHz., where signal strength drop is more noticeable. On the other hand the Padavan firmware seems more solid. Not at all sure why there's a difference in signal strength, and I didn't play with it much, but seemed to be weaker than what I got using Asus .342.

Didn't have any problems with WPA2/AES with Asus .342 firmware, though.