[hardy] networkmanager and WEP

[David Vincent]

Francisco Borges wrote:
> On Sat, Apr 5, 2008 at 5:11 PM, David Vincent <dvincent at sleepdeprived.ca> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>>  Hash: SHA1
>>  > But so far, using Hardy, I simply cannot connect to a WEP protected network.
>>
>>  Are you sure you're choosing the correct passphrase type?
>>
>>  WEP 128-bit Passphrase
>>  WEP 64/128-bit Hex
>>  WEP 64/128-bit ASCII
>>
>>  I had problems connecting to my WEP network until I realised I was not
>>  paying attention and had left it on the default "WEP 128-bit
>>  Passphrase".  NM would look like it was going to connect but then would
>>  fail.  WPA worked fine.  Finally I saw the "WEP 64/128-bit Hex" option
>>  and once I started using that everything was fine.
>>
>>  Just a thought.
> 
> I am sure I tried that. But I was always filling in a passphrase on
> the "WEP 128-bit Passphrase", and this key (generated from the
> passphrase on the router interface) on the "WEP 64/128-bit Hex".
> 
> What are you filling in in the Hex key field? An actual key you got
> from a phrase when configuring the router, or your actual passphrase?

i was being silly and relying on NM to figure things out for me and tell
me what type of key i had to enter - just like XP does.  NM doesn't work
like that.

i was entering my hex key into the 128-bit passphrase prompt (thats what
comes up by default) and my network would then fail to connect.  once i
corrected myself and added my hex key to the 64/128-bit Hex prompt
things of course worked like they needed to.

but now however, i find when i go to a hotspot and they give me a
key/passphrase to get on, i have to spend time trying all the options NM
gives before i find the one which works (which is annoying) unlike XP
which will just take my key and run with it, figure out what the network
requires and then use it.  that's annoying.  i haven't tried WICD yet -
anyone know if it fixes that issue?

-d