Is wep_key0 supposed to work as a string?

[Ben Greear]

I was trying to run hostapd on an ath5k system with
WEP enabled.

wep_default_key=0
wep_key0="ddd123"

Fails to set the key it seems, and I don't see anywhere
that converts the string to hex in the code:

wpa_driver_nl80211_set_key: ifindex=19 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=19 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=19 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=19 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=19 alg=1 addr=(nil) key_idx=0 set_tx=1 seq_len=0 key_len=6
nl80211: set_key failed; err=-22 Invalid argument)
Could not set WEP encryption.
vap0: Unable to setup interface.
Flushing old station entries
Deauthenticate all stations
rmdir[ctrl_interface]: No such file or directory
nl80211: Remove interface ifindex=36


If I use hex instead:

wep_key0=123456789a

it seems to work fine.


Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com