Bug 489 – Incorrect fragmentation with WEP enabled

Bug 489 - Incorrect fragmentation with WEP enabled

Summary:

Incorrect fragmentation with WEP enabled

Status:	VERIFIED FIXED

Product:	IPW2200
Component:	Fragmentation
Version:	0.16
Platform:	All All

Importance:	P2 normal
Assigned To:	James Ketrenos
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2004-12-14 01:57 by Sebastian Rosenkiewicz
Modified:	2005-10-05 13:16 (History)

Attachments
Sniffer dump (32.93 KB, text/html) 2004-12-14 02:04, Sebastian Rosenkiewicz	Details
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Sebastian Rosenkiewicz 2004-12-14 01:57:50

- load driver and configure AP with 64-bit WEP
- associate device with AP using WEP (iwconfig eth1 essid some_ap key open [1] 
1111111111)
- set fragmentation to 800B (iwconfig eth1 frag 800)
- send large PING from remote host to device (ping 10.72.2.102 -s 1000)

No PING is replied. Nothing appears in log. When using PING size of for eg. 
700B, device replies correctly.
Sniffer dump of incorrect WEP data packets is attached (00:0E:35:46:A1:8F is 
our BG device and 00:12:43:03:9D:60 is Cisco AP).

------- Comment #1 From Sebastian Rosenkiewicz 2004-12-14 02:04:27 -------

Created an attachment (id=173) [details]
Sniffer dump

------- Comment #2 From James Ketrenos 2004-12-20 08:53:18 -------

Fixed in 0.19

------- Comment #3 From James Ketrenos 2004-12-20 09:04:33 -------

Fixed in 0.19

------- Comment #4 From Sebastian Rosenkiewicz 2004-12-21 07:15:30 -------

Verified in 0.19.