Ticket #1391 (closed defect: fixed)
setting WEP key through iwconfig does not work
| Reported by: | thebohemian@… | Owned by: | openmoko-kernel@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | kernel | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: | buglog@…, sameo@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
It is currently not possible to set a WEP key using iwconfig:
root@om-gta02:~# iwconfig eth0 key "supersecret"
Error for wireless request "Set Encode" (8B2A) :
invalid argument "supersecret".
root@om-gta02:~# iwconfig eth0 enc "supersecret"
Error for wireless request "Set Encode" (8B2A) :
invalid argument "supersecret".
This was tested with the following kernel package on GTA02:
root@om-gta02:~# opkg status kernel-image-2.6.24
Package: kernel-image-2.6.24
Version: 1:2.6.24+git20080511-r
Attachments
Change History
comment:2 Changed 5 years ago by andy@…
- Cc sameo@… added
I try this on a belkin AP temporarily configure for WEP, the following works
iwconfig eth0 key e14a790fa60e1b9697abeb7368
iwconfig eth0 essid <AP SID>
BTW WEP is very insecure...
comment:4 Changed 5 years ago by graeme@…
Ah interesting, iwconfig eth0 key s:XXXXX works before iwconfig eth0 essid, but
not afterwards. This is clearly a bug.
Changed 5 years ago by sean@…
- Attachment wireless_ext.patch added
Fix to allow keys to be set after ESSID
comment:5 Changed 5 years ago by andy@…
Thanks for the super-rapid patch, stuck it in stable / andy / andy-tracking
comment:6 Changed 5 years ago by thebohemian@…
Hi,
this was very quick!
Just for the records:
There was no suspicious output in dmesg.
Prepending s: before the key has no effect.
Doing ifconfig eth0 down, then iwconfig eth0 key blabla works nicely.
Checking again when a new image with the proposed fix comes out.
(I think the bug's status can be changed to something else :) )
Anything in dmesg about it?