Author Topic: Connecting To Wep Network  (Read 2299 times)

jawZolife

  • Newbie
  • *
  • Posts: 13
    • View Profile
Connecting To Wep Network
« on: May 13, 2005, 06:49:51 pm »
Currently having trubs connecting to my secure network. I am unable to obtain a lease.

Cisco 1100 AP
SSID is not advertised
128-bit WEP is enabled

I have had success connecting to an unsecure wireless network (also 1100 AP)

I suspect my /etc/network/interfaces file is the culprit @ this point.

Anyone care to post their file so I may compare??

Any input is appreciated.

Thanks,
JawZ

----------------------------------------------
SL-6000L - OZ/Opie 3.5.3 (tosa)
CE-JC2 CF Expansion adapter
Various CF and SD cards
NuShield screen protection
PDA Panache stylus (never  again)

al_brain

  • Newbie
  • *
  • Posts: 6
    • View Profile
    • http://
Connecting To Wep Network
« Reply #1 on: May 26, 2005, 07:16:38 am »
I had issues connecting to my linksys W54G while in "Mixed" mode. When I changed it to 11, everying was fine, including WEP.

Al.

jamesm

  • Full Member
  • ***
  • Posts: 102
    • View Profile
    • http://
Connecting To Wep Network
« Reply #2 on: May 26, 2005, 08:12:19 am »
I don't know if this is the same issue, but there was a problem with Oz Opie 3.5.1 where the encryption tab of the wireless network config dialog was not actually applying any of the WEP settings.
This forum post describes the symptoms and suggests a workaround.
Victim of c3000 ebay scam.... Now after c3100

acpkendo

  • Full Member
  • ***
  • Posts: 169
    • View Profile
    • http://
Connecting To Wep Network
« Reply #3 on: May 27, 2005, 11:08:18 am »
If you are using a text WEP key (13 characters for 128-bit, IIRC), you need to prepend an "s:" to the key in the network settings.  E.g.:

Code: [Select]
s:abc0123456789
This tells the network scripts that it is a text key to be hashed out into hex.  If your key is 26 characters long, it should already be in hex, so nothing is needed.