Arch Linux

xaos5

Member

Registered: 2005-12-30

Posts: 75

wlan-ng 128bit WEP encryption issue [solved]

can someone explain to me what I have to do to let my wireless card use a 128bit encryption key? I've tryed messing with /etc/wlan/wlancfg-DEFAULT and saving it as wlancfg-linksys but still doesn't work. I can't dhcp with my routers wep encryption on. As of right now i'm using my wireless card (netgear ma111 - prism2_usb) without wep encryption.

wlan0     IEEE 802.11-b  ESSID:"linksys"  Nickname:"linksys"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:06:25:EC:8F:6B
          Bit Rate:11 Mb/s   Tx-Power:18 dBm
          Retry min limit:8   RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=37/92  Signal level=-51 dBm  Noise level=-88 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

is 128bit wep encryption possible or am I doing something wrong?

found this: http://64.233.179.104/search?q=cache:Mx … =clnk&cd=7
still no luck though....

EDIT: this stuff needs to be set

lnxreq_hostWEPEncrypt=true
lnxreq_hostWEPDecrypt=true
dot11PrivacyInvoked=true

key needs to be in XX:XX:XX:XX:XX and so on

AuthType="sharedkey"

in wlan.conf: SSID_wlan0= needs to be set to the file or default gets used.

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: wlan-ng 128bit WEP encryption issue [solved]

Back when I started with wlan-ng, I had similar problems, and came up with a different solution, which I'm still using - details here.

xaos5

Member

Registered: 2005-12-30

Posts: 75

Re: wlan-ng 128bit WEP encryption issue [solved]

that seems to be a lot more complicated then what I did because you had the same problem I did, without WEP encryption everything worked perfect. I guess what wlan-ng does is look for a file name wlancfg-<essid> which I did. The thing I didn't know how to do is enable WEP in the config file and make it use that file. In wlan.conf you must specify that otherwise it defaults back to wlancfg-DEFAULT which probably is something missing in the scripts.

From all the documentation I got from wlan-ng it decribes that it will take the network's essid (in my case linksys) and try to find the file wlancfg-<essid> which it wouldn't do. I had to specify it in wlan.conf to wlan0.

this seems like an almost common problem that should probably go into the wiki?

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: wlan-ng 128bit WEP encryption issue [solved]

that seems to be a lot more complicated then what I did

Depends on your point of view, I suppose. The way I see it, I have just one config file to deal with, and it's more transparent i.e. I can see the actual commands that are run.

Glad you worked it out, anyway.