Bug 16157 - Unable to enter hexadecimal WPA-PSK key
: Unable to enter hexadecimal WPA-PSK key
Status: UNCONFIRMED
Product: SqueezePlay
Classification: Unclassified
Component: Networking
: 7.5.x
: PC Windows XP
: -- enhancement (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-27 20:37 UTC by Cory Calvert
Modified: 2010-04-27 20:37 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 Cory Calvert 2010-04-27 20:37:38 UTC
This is somewhat related to bug #8371.

After trying to connect my new Squeezebox Radio to my wireless network, I found that I was not able to configure it with the encryption key for my network.  I have my wireless network configured with WPA1 PSK with AES encryption and a 64-character hexadecimal key.

My network is configured with a 64-character hexadecimal key directly, rather than using an ASCII passcode to generate the key.  The user interface on my Squeezebox Radio only allows entry of a ASCII passcode, up to 63-characters.

I was able to work around the problem by connecting the device via Ethernet, enabling SSH, and manually configuring the /etc/wpa_supplicant.conf file.  DHCP doesn't seem to work with my manual supplicant configuration, but it is fine with a static address.

I have the device working to my satisfaction now, but I figure that supporting 64-character hexadecimal keys would save other people the trouble of either mucking around in the console or rekeying their wireless network.

I realize that many or most people just use an ASCII passcode to generate their encryption key, but I am sure that I am not the only one who enters a key directly.

I am really impressed with the radio, BTW.  I like that I am able to get into it and work around things like this on my own. :-)