wep key does not work on wifi

Asked by rkhwulf

I am running Xubuntu 8.04 - when i key in the correct wep key for my wifi it tries to connect but cannot do so. It usually pops back up the box again to key in the wep key but still does not connect. Connects just fine to all open networks.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Connor Imes
Solved:
Last query:
Last reply:
Revision history for this message
Connor Imes (ckimes) said :
#1

Can you please tell us what wireless card you are using?
run and post the output of these commands:

lspci | grep Network
sudo lshw -C network
sudo iwconfig

Revision history for this message
rkhwulf (rkhwulf) said :
#2

Yes - I am using a d-link 2302 wireless pci card with an external super wifi antennae..

Revision history for this message
rkhwulf (rkhwulf) said :
#3

 Sorry - that is a D-link 2320 wireless pci card.

Revision history for this message
Connor Imes (ckimes) said :
#4

Give these links a try, the first one tells you that the card should work using the MadWifi Driver, and the second has more details about the driver:
https://help.ubuntu.com/community/HardwareSupportComponentsWirelessNetworkCardsDlink
https://help.ubuntu.com/community/WifiDocs/Driver/Madwifi

Revision history for this message
rkhwulf (rkhwulf) said :
#5

I think i am not making this clear enough. The D-link 2320 card (Atheros chip) is working just fine with the driver thar Xubuntu 8.04 puts on it. I am able to latch onto any unsecured wireless net work that is strong enough. However my next door neighbor has given me his WEP key and told me to latch onto his wifi which is much stronger than all the rest. When i attempt to latch onto his wifi, Xubuntu drops down a box for me to enter the real wep key into. After doing this the little spinning arrow at the top turns one ball green and keeps spinning but can't turn the other ball green. Then once again it drops down the box for me to enter the WEP key again and so on. This seems to me to be a problem it has in resolving the WEP key or something related to that. When you key in the WEP key you only have 2 choices for the network type - open system ot shared wep key. I have tried both but neither works. I hope this helps to diagnose the real problem.

Revision history for this message
Connor Imes (ckimes) said :
#6

I do understand what is happening, I have this problem on my Broadcom 4318 (though it won't connect to any network) - see https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/222197

In the second link I posted above, it mentions that for WEP, "When using a shared key, the driver must be modified with this command for it to work
       sudo iwpriv authmode 2"
For Hardy Heron, it says, "The drivers are in the restricted modules package; also see the madwifi-tools package.
       sudo apt-get install linux-restricted-modules madwifi-tools"

If you're willing, I would like for you to give this a try since this is from the Community Ubuntu Documentation. You can check to see if you are using the driver by running
       lsmod | grep ath_pci

Revision history for this message
rkhwulf (rkhwulf) said :
#7

Okay tried the command - sudo iwpriv authmode 2 - got this result - no private ioctls - and got the same results when i tried to connect to the WEP network.

Revision history for this message
Best Connor Imes (ckimes) said :
#8

Hmmm, it would seem the command is being used incorrectly. Here is a HowTo page for MadWifi, though you will not need to use everything on it (ex: you won't have to install it from source or any such thing) - http://madwifi.org/wiki/UserDocs/FirstTimeHowTo

You can probably start down at the section that has
iwconfig ath0 key <yourkey>
iwpriv ath0 authmode 2

You shouldn't need to make your own interface, you will probably use something like eth1 or wlan0 - run "iwconfig" to check for the correct interface. Have a read through that part, then skip down to the section entitled "Connecting to an AP with WEP". It's pretty straightforward, and if it doesn't work, it may be time for you to fill out a bug report here on Launchpad - https://bugs.launchpad.net/ubuntu
If you do fill out a bug report, post a link back here, and don't forget to post inside the bug report a link to this page, and include as much detail as you can, including hardware specs and the software you are using.

Revision history for this message
Connor Imes (ckimes) said :
#9

You can also click "Create bug report" in the upper left part of this page under Actions.

Revision history for this message
rkhwulf (rkhwulf) said :
#10

Thanks Connor Imes, that solved my question.