No matter what I set the WEP key to, I can't get it to use the non-default key in the router. Normal argument to iwconfig is:
iwconfig eth1 key [2]2702F22BBDE3E27D5CCBF46FEE
But setting wlassistant's WEP Key to "[2]2702F22BBDE3E27D5CCBF46FEE" must cause an error somewhere because iwconfig shows neither the key nor the key index changing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry that should have been:
[2]<space>key
.. but the problem still exists
I see from running from a console that it sends:
/sbin/iwconfig eth1 mode managed channel 6 key open [2] 2702F22BBDE3E27D5CCBF46FEE
which the man-page for iwconfig seems to suggest should work (their example: iwconfig eth0 key restricted [3] 0123456789) so this appears to not be a wlassistant bug after all.
Cheers!
Rick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No matter what I set the WEP key to, I can't get it to use the non-default key in the router. Normal argument to iwconfig is:
iwconfig eth1 key [2]2702F22BBDE3E27D5CCBF46FEE
But setting wlassistant's WEP Key to "[2]2702F22BBDE3E27D5CCBF46FEE" must cause an error somewhere because iwconfig shows neither the key nor the key index changing.
Sorry that should have been:
[2]<space>key
.. but the problem still exists
I see from running from a console that it sends:
/sbin/iwconfig eth1 mode managed channel 6 key open [2] 2702F22BBDE3E27D5CCBF46FEE
which the man-page for iwconfig seems to suggest should work (their example: iwconfig eth0 key restricted [3] 0123456789) so this appears to not be a wlassistant bug after all.
Cheers!
Rick
well, it actually IS a wlassistant problem and the way it's passing arguments to iwconfig. Will fix in the next release. Thanks for bringing it up!