Bugzilla – Bug 8308
Allow wireless config via SC wired connection
Last modified: 2008-12-18 11:42:31 UTC
My Transporter was working fine on my wireless WPA-protected network, but due to server problems I ended up building a new system. Long story short, I had to use SC version 7.1 because 7.0 didn't have the correct version of perl support for my Linux Fedora 9 system. (The server is wired, I have laptops and Transporter itself that use the wireless access, why SqueezeBox V3 works fine) Transporter was unable to play any music, though it could navigate my music library etc. I did a "return to factory settings", but then was not able to enter the 64 hex-digit WPA key... I could only enter 63! I connected the Transporter via wire cable, d/l new TP firmware (42) hoping that would allow me to enter the full key. Instead, the key area was filled with asterisks and I could not figure out how to change it. Suggestion: Allow configuring the wireless things (SSID, key, etc) via the SqueezeCenter Web interface... Obviously this will require a wired connection to begin with, but it would also be a lot simpler to enter the key from a regular keyboard. And easy to have an option to enter a "hex key" or a "text phrase". I spent more than an hour trying to enter the key correctly using the remote, and checking, rechecking, and checking again, the key.. all to no avail. :-( PS. I flagged this as "critical" because right now it is impossible to enter the correct wireless key.. though it was working with SlimServer... If my suggested enhancement could be implemented in one of the 7.1 nightly builds, that would help immensely. :-) Cheers, Don Russell
please do not preset the target fields. These are used by QA after a review.
(In reply to comment #1) > please do not preset the target fields. These are used by QA after a review. Oh. Sorry 'bout that. :-) Other than that, is the suggestion sound? (pun intended) :-)
Moving this to a SqueezeCenter bug from Transporter. Don: to solve your problem, do a factory reset on the Transporter, that will remove the stored key, which will let you enter a new key.
(In reply to comment #3) > Don: to solve your problem, do a factory reset on the Transporter, that will > remove the stored key, which will let you enter a new key. That did not work. I did the factory rest, got to setting up the wireless access, selected my SSID, and was prompted to enter my WPA2 key: Nothing worked on the remote... and not 5 seconds later, Transporter restarted and I went through the same process several times. So, I'm back to being unable to use my Transporter. :-(
Changed Hardware/OS to "All", since the concept/suggestion is not architecture-dependent. Since I'm unable to use the Transporter at all in a wireless environment, can we bump the severity/priority up a notch or two?
The main part of this bug _is_ a firmware bug (for Squeezbox and/or Transporter) to allow network configurations via the network. This is a dup of bug 6684, then, and would use Robin Bowes' UDAP plugin for the SBR to set up SB3 and TR devices. *** This bug has been marked as a duplicate of bug 6684 ***
IMHO there are two entirely seperate issues here: 1) Allow wireless setup via the wired connection (via UDAP/SC Plugin/Mini webserver/whatever) 2) Allow entry of WPA keys as Hex (64 chars) vs ascii (63 chars) 2 seems like a bug to me (and is nothing to do with 6684), 1 is an enh (and related to 6684). Just my 2c.