Hello.
I am new to Linux. I have just installed OpenSuse 11 on my old laptop. Everything is fine, except that I can’t connect to my secured wireless network. It is secured with a 64bit WEP encryption, with a passphrase.
I ran everything as described in the sticky thread. All is right. If I remove the wireless security, I can connect.
I used Yast to set the network up. I select “Managed” type and WEP-Open. I input my passphrase. In WEP keys, I selected 64 bits.
At reboot, it doesn’t connect. Am I doing something wrong ?
I am copying the standard info:
/usr/bin/lsusb
Bus 004 Device 001: (Channel 11)
Quality=54/100 Signal level=-35 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Extra:tsf=0000000cc59be4d7ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 2001:3c00 D-Link Corp. [hex] DWL-G122 802.11g rev. B1 [ralink]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
WEP passphrases are a problem as there are at least two different ways to
convert the phrase to a key. The only surefire method is to use a passphrase on
your router, but then copy the key and use it everywhere else.
Thanks, Larry.
I tried to put the hexadecimal key thru Yast, but after reboot it didn’t connect to my network.
I looked at knetworkmanager to try to connect manually. I noticed that it is not possible to input a 64 bit key. It only proposes 128 bit ones. Is there a way to add the 64 bit options ?
By the way, do I need to reboot at any attempt, or should it work without ? I set the activation on Hotplug.
I found this thread because I had a similar question, and I was disappointed that there was no answer. But I just managed to configure my 64bit wep key successfully. I used Yast and checked the flag to use Kinternet then setup the wep key in yast as a 10 digit hexadecimal. I then configured Kinternet used the openweb 40/128 even though I was using the 64bit wep then entered the 10digit hex key again. It worked!
When I went back in and looked at the key in Kinternet it had replaced it with the essid for some reason. I figured that it was because I had entered the 10 digit key in yast. I then tried to remove the key from yast and just have the key in Kinternet so that I could easily configure more than one encrypted access point. That worked too. It did complain in yast and ask if I really did want to use no encryption and I said yes or otherwise completed the configuration. Then in kinternet I added the 10 digit hex key for the appropriate access point and it left it there and connected with encryption.
So I it appears that the 128 encryption supports the 64 bit encryption if you just enter the 10 digit key appropriately.