Bug 1078 - DUT still sends OPEN-NONE ad-hoc beacons after changed from OPEN-NONE security to OPEN-WEP 64bit.
: DUT still sends OPEN-NONE ad-hoc beacons after changed from OPEN-NONE securit...
Status: VERIFIED FIXED
: IPW3945
IBSS
: 1.0.8
: All All
: P1 minor
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2006-06-22 04:47 by
Modified: 2006-08-27 23:24 (History)


Attachments
Patch to try; modifies beacon fill function to set privacy based on client vs. association request (905 bytes, patch)
2006-06-22 07:37, James Ketrenos
Details | Diff
Sniffer capture of the connection after applying the patch (505.87 KB, text/plain)
2006-06-23 13:30, Nick Wallace
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2006-06-22 04:47:24
Summary:
DUT still sends OPEN-NONE ad-hoc beacons after changed from OPEN-NONE security 
to OPEN-WEP 64bit.
Environmet:

OS Version is SUSE10 with 2.6.15.3 kernel, Wireless Tools(Rev. 28 pre13)

Failure Rate:	100% 3/3

Steps to Reproduce	
1. Load wireless driver module.
2. On DUT, use the command: iwconfig eth1 essid AD mode ad-hoc channel 1 to 
create ad-hoc network.
3. Check DUT create ad-hoc network successfully.
eth1      IEEE 802.11g  ESSID:"AD"
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 02:13:02:41:46:32
          Bit Rate=1 Mb/s   Tx-Power:15 dBm
          Retry limit:15   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:60  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:16   Missed beacon:0
4. On partner system(an Windows XP), the SSID with OPEN-NONE security shows.
 
5. Change the adhoc security to OPEN-WEP 64 bit on DUT with iwconfig eth1 key 
0123456789, then check the information as following:
 eth1      IEEE 802.11g  ESSID:"AD"
          Mode:Ad-Hoc  Frequency:2.412 GHz  Cell: 02:13:02:41:46:32
          Bit Rate=1 Mb/s   Tx-Power:15 dBm
          Retry limit:15   RTS thr:off   Fragment thr:off
          Encryption key:0123-4567-89   Security mode:open
          Power Management:off
          Link Quality:60  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:637   Missed beacon:0
6. Scan the SSID on partner system, the SSID still shows OPEN-NONE security.

Verification	
1. This problem is also observed on OPEN-WEP 128bit.
2. This problem is NOT observed after changed the channel on DUT. 
3. This problem is NOT observed after changed the band on DUT.
4. This problem is NOT observed on create the ad-hoc directly on DUT with the 
command iwconfig eth1 essid AD mode ad-hoc channel 1 key 0123456789.

Comments	
Sniffer file attached. DUT MAC 00:13:02:00:C3:29.
------- Comment #1 From 2006-06-22 07:37:21 -------
Created an attachment (id=836) [details]
Patch to try; modifies beacon fill function to set privacy based on client vs.
association request

This patch modifies the fill_beacon function such that it sets the privacy
capability based on the client configuration vs. the association request used
to create/associate to the network.
------- Comment #2 From 2006-06-22 16:40:16 -------
After additional testing using the patch attached to this page, this bug seems 
to be resolved.

The SSID scan on the partner system shows the SSID as open wep.
------- Comment #3 From 2006-06-23 13:30:27 -------
Created an attachment (id=842) [details]
Sniffer capture of the connection after applying the patch
------- Comment #4 From 2006-06-23 15:51:01 -------
Merged for 1.0.11.  Setting as fixed.
------- Comment #5 From 2006-08-23 23:58:45 -------
Nick,

Can you verify this bug?
------- Comment #6 From 2006-08-24 09:54:51 -------
The capability information in the beacon and the settings of the ssid in 
Windows show that the network broadcasts Open/Wep. 

Fix Verified.
------- Comment #7 From 2006-08-27 23:24:10 -------
Verify it based on comment #2.