Bug 11066 - Unable to complete setup on non-broadcasted SSIDs wireless networks
: Unable to complete setup on non-broadcasted SSIDs wireless networks
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: unspecified
: PC Windows XP
: P1 major (vote)
: 7.4.0
Assigned To: Felix Mueller
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-12 12:32 UTC by Julius Dauz
Modified: 2009-10-05 14:30 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julius Dauz 2009-02-12 12:32:48 UTC
Currently, when you attempt to connect to a non-broadcasted SSID, the setup allows you to enter the SSID, select an encryption type, enter in the key/password, then attempt the connection.

Should we change it so, once you enter in the SSID, the setup scans networks right away to make sure that there is a network with that name instead of having the user go through the entire network setup only to find out later that something was entered incorrectly?
Comment 1 Jim McAtee 2009-02-12 14:34:11 UTC
If you did that then wouldn't it also be unnecessary to enter the encryption type?  That would be a good thing.
Comment 2 Richard Titmuss 2009-02-13 02:36:44 UTC
Right, but if you are not broadcasting the SSID we can't scan for it. If you hide the SSID you are prevented finding the network via scanning.

Marking this as invalid, unless anyone has a bright idea on how this could be implemented.
Comment 3 Blackketter Dean 2009-02-13 06:32:08 UTC
Julius: are you suggesting that the user might enter the SSID for a network that isn't actually hidden?  Or that you suspect that there may be a way to detect the encryption type of a hidden network?
Comment 4 Mickey Gee 2009-04-14 13:36:29 UTC
Wanted to reopen and discuss some more due to high-priority Duet bug fixing discussions and beta tester on forums:

"But another thing, I somehow changed my network config (made SSID invisible) after wireless connection and before the SBT update, now it can not reach mysqueezebox.com I took back the changes. It still cannot reach it, and there is no way for me to change the network setup or ignore the error and continue (like JJZolx suggested). I know this is not a typical usecase, but it is still a dead-end in the setup just like in the case of self-assigned IP address.

Rudolf"

Marked with MP target to ensure it gets discussed soon.
Comment 5 Mickey Gee 2009-04-14 13:46:52 UTC
See corresponding Duet bug 8129.
Comment 6 Mickey Gee 2009-04-15 11:40:32 UTC
Moving to post-MP per today's discussion.
Comment 7 Blackketter Dean 2009-07-22 09:01:52 UTC
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code.  Feel free to move it back if it's specific to the original product.
Comment 8 Felix Mueller 2009-08-09 05:57:17 UTC
Connecting to a network with hidden SSID should now work for all squeezeplay based products (Fab4, Baby and Jive). 7.4 r6976

Still open is the case where a previously shown SSID is hidden after setup which prevents further successful connections. But that is covered in bug 8129.
Comment 9 James Richardson 2009-10-05 14:30:54 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

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.