Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1685 (new defect)

Opened 14 years ago

Last modified 14 years ago

Unable to send traffic when WEP key has been modified.

Reported by: anonymous Assigned to:
Priority: major Milestone:
Component: madwifi: driver Version: v0.9.3.1
Keywords: Cc:
Patch is attached: 0 Pending:

Description (Last modified by mentor)

I am using an Atheros chip with madwifi driver version 0.9.3.1. The steps which I am using to reproduce the bug are as follows:

Initially access point is using the key: 012345678

So to enable the wireless on client end, using the following set of commands: 

insmod /lib/drivers/wlan.ko
insmod /lib/drivers/wlan_wep.ko
insmod /lib/drivers/wlan_scan_sta.ko
insmod /lib/drivers/ath_hal.ko
insmod /lib/drivers/ath_rate_sample.ko
insmod /lib/drivers/ath_pci.ko
iwconfig ath0 mode managed essid ankit008 key 0123456789 key open
ifconfig ath0 192.168.204.52
ifconfig ath0 up

After this I am able to send traffic to the access point and every thing works fine.

Now the key on the access point is changed to 1111111111, so I execute the following sets of commands on the client: 

ifconfig ath0 down
iwconfig ath0 mode managed essid ankit008 key 1111111111 key open
ifconfig ath0 up

After this I am not able to send traffic to the access point. When I take a tcpdump on the access point then I see few sap(?) packets are coming from the client end. Although when I used iwconfig at client end I am able to see the changed key settings.

Change History

12/04/07 16:04:39 changed by mentor

  • description changed.

12/04/07 16:06:11 changed by mentor

  • description changed.

(follow-up: ↓ 4 ) 12/04/07 16:06:50 changed by mentor

Are you able to reproduce this with trunk?

(in reply to: ↑ 3 ; follow-up: ↓ 6 ) 12/05/07 13:59:34 changed by anonymous

I am able to reproduce this bug every time when i change the key with 0.9.3.1 version.

Replying to mentor:

Are you able to reproduce this with trunk?

12/06/07 13:20:08 changed by anonymous

There is one more update if i do not use ifconfig ath0 down command at client side when changing the key the connection will work properly.

now to change the key at client side i used the following command

iwconfig ath0 mode managed essid ankit008 key 1111111111 key open ifconfig ath0 up

Can you tell me what is wirong with ifconfig ath0 down. As i know to change settings we need to down the interface first.

(in reply to: ↑ 4 ) 12/06/07 20:12:53 changed by mentor

Replying to anonymous:

I am able to reproduce this bug every time when i change the key with 0.9.3.1 version.

Yes, but are you able to reproduce it with the latest code from subversion trunk?