[driverloader] yeah!! it works TINET1130
marc at linuxant.com
Fri Feb 6 19:33:16 EST 2004
On Feb 6, 2004, at 6:10 PM, Jim wrote:
> Marc Boucher wrote:
>> On Feb 6, 2004, at 3:12 PM, Dan Allen wrote:
>>> Jim (jsw at wadell.org) wrote:
>>>> Thanks for your post. The tip about KEY= \ open fixed a problem I
>>>> been messing with for
>>>> some time. Where did you find the infomation?
>>> In my head ;) It is amazing the ideas you have after many hours of
>>> starng at a terminal. It begins to speak to you.
>> The \ prevents the shell from interpreting the space as a delimiter,
>> and is documented in the manpage for bash(1).
>> Alternatively you can include the whole thing in double-quotes, like
>> KEY=".... open"
> I was more interested in the "open" phrase. I could not find it!
The "open" option is mentioned in our FAQ at
10. I am having problems with WEP.
You have to make sure that you are using the same WEP settings on your
access point and on your client side.
Some versions of the wireless-tools have been compiled with a
different interface than the kernel. Use "iwconfig --version" to
verify that they match. If not, your wireless-tools package might need
to be updated.
There are sometimes compatibility problems when the Access Point key
mode is set to "automatic" so you can try to choose "open system" or
"shared key" instead.
Add the keyword "open" after your 64 or 128 bit WEP key when using
the command "iwconfig" to configure your client in "open system" mode.
Add the keyword "restricted" after your 64 or 128 bit WEP key when
using the command "iwconfig" to configure your client in "shared key"
e.g.: iwconfig key $key restricted
(replace $key with your real encryption key)
I guess that it could be improved by including the syntax for adding
those parameters to the interface's config file.. We'll look into doing
More information about the driverloader