Bugzilla – Bug 768
setting security mode to 'restricted' has no effect if key is off
Last modified: 2005-10-27 02:37:29
You need to log in before you can comment on or make changes to this bug.
I don't know if this is intended behavior, but I am requesting that it be changed. When one issues these commands, in order: % iwconfig eth0 key open % iwconfig eth0 key off % iwconfig eth0 key restricted % iwconfig eth0 key on it seems that the security mode is still set to 'open'. If one reverses the last two commands, the security mode is correctly set to 'restricted'. It seems that choosing open/restricted has no effect when the key is off. This is bad, e.g. because the waproamd scripts issue the 'restricted' command before turning the key off, hence it doesn't properly associate with shared-key access points. When I re-arrange the commands in the script, everything works fine. But I believe that proper ipw2200 behavior would be to make changes in the security mode 'stick' even when WEP is off.
Created an attachment (id=506) [details] fix patch
Will be applied to next release, per James. Marking as fixed.
I check with these several modes. It can be set to restricted security mode with the command "iwconfig eth0 key restricted" Verify on V1.0.8.