Bug 771 - Too many (8) bytes recieved when using AES/hwcrypto
: Too many (8) bytes recieved when using AES/hwcrypto
Status: VERIFIED FIXED
: IPW2200
Data Transfer
: 1.0.6
: All All
: P2 major
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-09-06 12:05 by
Modified: 2006-02-28 00:03 (History)


Attachments
fix patch (1.04 KB, patch)
2005-09-07 22:49, Zhu Yi
Details | Diff


Note

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


Description From 2005-09-06 12:05:40
Hi,
When using AES with hardware crypto enabled, the ipw2200 driver returns
too much data (8 bytes) in all received data. When I look at received
data with ethereal, there are 8 null bytes after all TCP, UDP or other
data. When hardware crypto is disabĺed or TKIP is used, this problem
does not occur.
Ever since hwcrypto was enabled by default, I got this message from
ISC DHCP client (3.0.1):

DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
ip length 576 disagrees with bytes received 584.
accepting packet with data after udp payload.
DHCPOFFER from 192.168.22.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPREQUEST on eth1 to 255.255.255.255 port 67
ip length 576 disagrees with bytes received 584.
accepting packet with data after udp payload.
DHCPACK from 192.168.22.1

I'm using a WRT54G AP and using WPA2/AES,
Debian Sarge
wpa_supplicant 0.4.0
linux 2.6.12

/Peter
------- Comment #1 From 2005-09-06 20:31:06 -------
Are you sure you are using 1.0.6 driver? We did have this problem in the early
version of the driver.
------- Comment #2 From 2005-09-07 13:01:54 -------
Sorry, I forget to check this; I have 1.0.6, but with the patch from Bug #729:
http://www.bughost.org/bugzilla/attachment.cgi?id=467
Without this I cannot connect with WPA(2)/AES, it will disconnect as soon as
I receive anything from my AP.
So maybe I should have added a comment to Bug #729 instead.
------- Comment #3 From 2005-09-07 22:49:32 -------
Created an attachment (id=517) [details]
fix patch

Ah, I see the problem. Thanks for reporting. Please try this fix.
------- Comment #4 From 2005-09-07 22:49:52 -------
mark as fixed
------- Comment #5 From 2006-02-28 00:03:41 -------
Since there is no update for long time and we do not find this problem against 
ipw2200_v1.0.13, verify this bug.
If anyone finds this problem again, please reopen.