Bug 4465 - SB3 can not connect to Belkin F57231-4 Wireless G+ Router
: SB3 can not connect to Belkin F57231-4 Wireless G+ Router
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 64
: All All
: P2 major (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-03 14:16 UTC by Edward George
Modified: 2006-11-28 00:41 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edward George 2006-11-03 14:16:03 UTC
Replaced my old router today with a Belkin Wireless G+ Router (F57231-4)...
 
My SB3 (using firmware 64 from slimserver 6.5.0) will not connect to it at all.
I have tried turning off all turbo features, all protection modes etc to get it as basic as possible.
I tried using WPA-TKIP, WPA2-AES and with no security on at all. All with no success.
I have tried the router running on several different channels.
I have checked and double checked the passkey and SSID numerous times.
MAC Filtering is not enabled.
None of my other wireless devices have any problem connecting. 
Signal strength is reported by my laptop as excellent when next to the SB3.

Connecting fails with the message: "Problem: Cannot find specified wireless network"
Comment 1 Edward George 2006-11-03 14:24:39 UTC
Ok. I have sorted it. 
Tried it one last time and noticed there were two entries for my network in the list of detected networks. One wouldn't connect, which is the one i had been trying. Selecting the other entry and it connected fine.
Comment 2 Chris Owens 2006-11-10 13:21:05 UTC
I'll just throw out some ideas of other users run across this.

The Squeezebox stores the name of recent wireless networks even if it doesn't see an SSID broadcast from them at the moment.  Trying to connect to them will fail if they are not active.

It sounds like there might still be a bug here, though, in that if there is an SSID broadcast, the SB3 should not ALSO present a stored network of the same name.  I'll keep an eye out for that behavior and file it as a separate bug if that seems to be the case.

I'm glad you got yours working, Edward.
Comment 3 Edward George 2006-11-10 13:41:31 UTC
I think what may have happened is that I originally had SSID broadcast off when configuring so I had to enter the SSID myself (I turned the broadcast on later during my attempts at getting it to work). The entry screen already had characters in so I had to enter whitespace at the end. 
There didn't seem to be a way to delete the characters other than adding whitespace to overwrite them.

Is it possible that when probing for the network it includes the whitespace in the id?
Comment 4 Chris Owens 2006-11-27 17:43:40 UTC
yes indeed.  The whitespace character is a valid character in a WPA passcode so we have to recognize it!  

However the remote does not have a 'delete' button!  Our solution to this is documented in the little owners' guide (page 7 near the bottom), but I don't know if it's documented anywhere else.

I'll put it in here for other customers' reference as well.

In WPA password-entry mode, the 'ADD' button on the remote functions as a 'delete' key.  So if you have entered 'foobar' and it turns out the correct password is 'barbaz' you can use the arrow keys to go out to the end of the password, and 'ADD' to delete the old password.

This is also true in one or two locations after connecting to Slimserver.  If the 'ADD' key doesn't make sense, but you need a 'delete' key, the 'ADD' key usually contains that functionality.
Comment 5 Jim McAtee 2006-11-27 22:09:50 UTC
Honestly, how many people are going to have trailing spaces in either passwords or SSIDs vs the number that do exactly what Edward did?  I did the same thing the first time I entered a password into the Squeezebox because I had no idea where the bloody Delete function was hidden.  You'd probably save a number of people a lot of grief by just chopping trailing spaces from the entered string.  See bug 2695.
Comment 6 Edward George 2006-11-28 00:36:40 UTC
(In reply to comment #4)
> yes indeed.  The whitespace character is a valid character in a WPA passcode so
> we have to recognize it!  

No, this wasn't the password entry, this was the SSID screen
Comment 7 Edward George 2006-11-28 00:41:34 UTC
> This is also true in one or two locations after connecting to Slimserver.  If
> the 'ADD' key doesn't make sense, but you need a 'delete' key, the 'ADD' key
> usually contains that functionality.
> 

Ah, as there was no delete key I expected it to have the same behaviour as the other entry screens on the squeezebox where pressing back (left) deletes the last character (eg the search screen)