Xbox360 wireless N adapter can't connect while using WPA2

[Ernesto<asotaku@…>]

When encrypting the wifi network with WPA2, the Xbox360 wireless N adapter is unable to connect to the fonera N with the 2.3.6.0 firmware. It works with WPA, though.

With the previously available firmware, Xbox360's wifi was connecting successfully with WPA2. These issues have started since I upgraded to 2.3.6.0.

[Josemi <josemi@…>]

Same problem here, I was going to report it.

This is really annoying.

[matthijs]

I guess the XBox doesn't give any more specific error than "can't connect"? Does the network show up in the list at all?

Perhaps this is an issue similar to #540? Could you try the workaround in  http://trac.fonosfera.org/fon-ng/ticket/540#comment:12 and report here if it changes anything?

[Josemi <josemi@…>]

It says (not literally translated from spanish): XBOX was unable to connect to the network, and if you click on more information it ask you to reboot the router and verify that the password is correct.And anything else.

I didn´t understand the second part, Are you asking me to run root@Fonera:~# wget -O /lib/wifi/rt3052.sh  http://trac.fonosfera.org/fon-ng/export/1679/tags/2.3.0.0/fon/ra_wifi/files/lib/wifi/rt3052.sh? If the answer is yes, I will try it.

If you want to, I also can do some live debugging, Im connected right now to #fonosfera IRC Channel.

[matthijs]

Yes, please run that command to see if it changes anything.

[Josemi <josemi@…>]

Continue not working

[matthijs]

Could you get a logread and dmesg output from shortly after a connection attempt?

[Josemi <josemi@…>]

I am on IRC right now, do you want me to run root@Fonera:~# wget -O /lib/wifi/rt3052.sh  http://trac.fonosfera.org/fon-ng/export/1679/tags/2.3.0.0/fon/ra_wifi/files/lib/wifi/rt3052.sh before trying to connect and logread and dmesg?

[Josemi <josemi@…>]

After running wget -O /lib/wifi/rt3052.sh  http://trac.fonosfera.org/fon-ng/export/1679/tags/2.3.0.0/fon/ra_wifi/files/lib/wifi/rt3052.sh, and rebooting fonera, I´ve tried to connect the XBOX, continues giving same error.

logread:  http://pastebin.com/yqnWNUjJ dmesg:  http://pastebin.com/cGmxWCTr

[matthijs]

I've just confirmed with Josemi on IRC that the DHCP request shown in the log is in fact his laptop, not the XBOX...

[Josemi <josemi@…>]

I continue having the same problem on 2.3.6.1 RC :-( I cannot connect my XBOX to the Internet through Wi-Fi

[sibilio@…]

Confirm I have the same problem with 2.3.6.0 and 2.3.6.1. "MyPlace?" is detected but XBOX360 is unable to connect to the network

[matthijs]

#1055 reports a similar, perhaps identical issue.

[matthijs]

#1055 is a duplicate of this issue.

[jgbreezer@…]

Hoping adding this entry will put me on CC list (or I'll properly create a user if thats what I need to do, then add myself CC'd).

Seeing same issue, with release 2.3.6.1. All other devices I own connect to fonera router fine, though all using 802.11b/g; xbox 360s (slim) still complains if I set router to b/g only. Am a Linux c++/python developer, can help with reporting/debug if needed. Is it worth trying the latest beta which I think I saw as 2.3.7.0 earmarked version?

[anonymous]

Shoulda commented earlier, but after a couple of weeks I had the spare time to try out the newest 2.3.7.0 release (I'm using the dev one but the other one's probably the same) and it worked fine, so my Xbox 360 slim can connect with 802.11n and all other wifi seems happy too.

Yay! I was hating having to have the other WAP in the house running ('g' only) just for the console / considering a cable all the way.. Can turn it off now.

The router seems fairly stable - only rebooted it manually once since then (several months ago) though the power did trip out for enough of a second to reboot it the other day (and require reset on some clocks/computers grrrr...!)

Once 2.3.7.0 goes properly stable and released, should be able to close this ticket!

[matthijs]

Thanks for testing the latest beta! I'll go ahead and close this report now already, since the issue is fixed in the subversion repository apparently. I suspect the wifi driver upgrade fixed this issue.