Bugzilla – Bug 13234
Baby will not connect using WPS to a Netgear WNDR3300, WNR3500 consistently
Last modified: 2009-10-22 11:23:31 UTC
Baby tested with firmware r6895 and r6899 Baby will not connect to the router using Push Button Method. I have tried both hardware push button and software Push button method.
This also fails using PIN method.
There does seem to be an issue here, I'll try to narrow this down and attach some logs. I'm noticing that WPS push button seems to connect consistently for me with the WNDR3300, however the PIN method only works about 1:3 times. The other 2:3 times the router says the device is connected successfully and the baby spinny continues forever.
I did the same tests with Baby on a Netgear WNR3500 (latest FW) and had mixed results. Using the "Soft Push Button" it worked the first time, the failed twice. The failures occured in the same fashion. The Netgear Admin Page said the device connected, but the Baby continue to spin trying to connect. When using the "Pin" method, I experienced similar issues. First try, the Netgear Admin Page said that the connection was established, but the Baby continued to spin and attempt to connect. I ended up resetting to factory defaults and tried again. Second try, the Netgear Admin Page timeout during the Pin connection and it displayed a "Internet Explorer could not load the page" error and the Baby continued to spin trying to connect. It worked the third time.
Fixing mid-air-collision.
*** Bug 13257 has been marked as a duplicate of this bug. ***
Created attachment 5576 [details] tail -f log
How important is this? It is marked P2. If we know it works on most wireless APs and the ones with problems are a small part of the market, keep it a P2 and STOP WORKING ON IT. If this does happen on a significant % of the market (5% or more), make it a P1 and keep working.
Ross: Unfortunately the log doesn't reveal a lot except that it looks to me that Baby didn't even try to connect. Hmm. I have a WNR3500 here and WPS works fine. I can't tell about the other router though. Pat: I cannot judge about the market share of a particular router make and model, but keep in mind that it might be different in the US and Europe. When we continue working on this bug I need additional information about the firmware and settings of your WNR3500 so I can try the same here. As a general note please be advised that only one WPS connection attempt is allowed at the time. So if for instance you and Steven are trying at the same time it will always fail. Maybe it would be a good thing if you get a non Logitech WPS client to compare the general performance regarding WPS in MV with all your wireless gear active.
Created attachment 5579 [details] another messages.log Felix how many times did you try? I just tried twice, the first time it worked perfectly, the second time several minutes have passed the router indicates the player is connected and baby is spinning extremely slowly. I'm the only one in the office testing WPS at the moment, I'm able to reproduce this within a few tries. I'm testing using PBC method, WPA2 encryption, and I changed the SSID to the model number of the router. All other router settings are left at default.
MP r6947.
Ross: I tried several times. The error in the log is from the kernel and looks related to wireless and maybe is also related to WPS, but I cannot tell for sure. Richard asked Remy for help about the kernel oops and we need to investigate, but I am afraid there is not quick solution.
Connecting to an AP often failed due to the kernel oops caused by improper use of semaphores in the wireless driver under RT Linux. The issue has been fixed by Remy and Richard. Please retest with latest Baby firmware.
Ross: please retest with latest 7.4.1 firmware
This bug has been marked as fixed in the 7.4.1 release version of SqueezeBox Server! Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.