Bugzilla – Bug 13025
Wireless connectivity intermittent
Last modified: 2009-09-08 09:20:10 UTC
From CAT tester Marc Marcuse: It started out fine, I connected to my home network. Then it dropped to no networks other than mine viewed, but it rejected my (correctly typed) WPA2 password. Now it doesn’t detect ANY wifi networks when there are over 10 wireless networks in my apartment that I can easily see using other means. It won’t see any of them. Factory reset got it to view all networks again, but still won’t connect with my router anymore, I get a can’t connect with the password error. I have a Buffalo WHR-G125 but it’s got DD-WRT on it. I was able to connect fine at first, but now it’s a no go (I have open IP’s available and other Wifi connections running fine to it). I broadcast SSID, yes. And I did the factory reset through the unit. Settings >> Advanced >> Factory reset (or something like that). Now that I’m reset and can’t connect to a wifi router, I’m stuck at the connection screen and can’t access menus anymore. I let it sit for a few hours off, then turned it on and rescanned and it found the whole batch of wifi networks in my area now. I think there may be a network caching issue, I can rescan a bunch of times without it noticing every network and then magically a whole slew of them show up (over the course of 15 minutes). And we’re talking about 2-3 bars signal strength so it’s not a signal fluctuation. Well, now I can connect to my neighbor’s open network which it couldn’t before. But I still can’t connect again to my WPA2 personal wifi, it says the password is incorrect, which it certainly is not. I have no idea how to fix this, it’s a blocking issue for me. Yes, this unit absolutely overcaches the wireless network info. I’ll unplug the router and it’s still in the list 15 minutes later! How do I force a hard rescan? When I plug in a new router, it doesn’t find it unless I reset the Squeezebox. To top it off, I took my router and removed the security on it - and the Squeezebox still asks for a password to connect to it. You guys need to be a little less hard with the caching on network names/passwords and initiate a fresh scan (or at least allow a force rescan option). So as of right now, I’m dead in the water.
We need to find out what firmware revision Marc Marcuse Baby currently has.
Some CAT users are reporting wireless issues solved with 6758 firmware. This guy hasn't reported anything, so we'll continue monitoring.
(In reply to comment #2) > Some CAT users are reporting wireless issues solved with 6758 firmware. This > guy hasn't reported anything, so we'll continue monitoring. Probably due to Felix's TKIP fixes, see bug 12924.
Mickey: Any more negative reports or issues? Ever heard back from this guy?
I did a search of the CAT forums and problem reports. No more news from this guy. I suspect things are better with the newer firmware. Will close for now. Will ask CAT testers to factory reset and go through setup again in a few days, and will see whether wireless issues reappear.