linux-kernel - Re: 2.6.27-rc3-git6 iwl3945 driver drops packets with WEP enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 20 Aug 2008 22:27:15 -0600 (MDT)
From:	jmerkey@...fmountaingroup.com
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	jmerkey@...fmountaingroup.com, linux-kernel@...r.kernel.org,
	linux-wireless@...r.kernel.org
Subject: Re: 2.6.27-rc3-git6 iwl3945 driver drops packets with WEP  enabled

> On Wed, 20 Aug 2008 11:27:02 -0600 (MDT)
> jmerkey@...fmountaingroup.com wrote:
>
>>
>> On an Acer 9410 laptop with dual core processors, the iwl3945 driver has
>> intermittment receiver lockup problems (stops receiving packets) using
>> the
>> Linux iwl3945 drivers with WEP encryption enbaled.  The adapter works
>> fine
>> without WEP or WPA.   If the same system is booted to Windows Vista
>> (which
>> takes about 15 minutes to boot because Vista is a fat slow pig) the
>> wireless drivers work fine with WEP under Vista on the same system.
>>
>> If the system copies the ndis .sys drivers and I build ndiswrapper
>> (which
>> has to be really hacked up to build on 2.6.27) and use the ndis drivers
>> on
>> 2.6.27-rc3 with a modified ndiswrapper, they work fine.
>>
>> I suspect the firmware or an interaction with the firmware settings
>> since
>> when the system is booted to Vista after running 2.6.27-rc3 with the
>> iwl3945 drivers, I have to power cycle the system periodically after
>> running the iwl3945 driver to get the drivers under Vista to work again,
>> but not always.
>>
>
> (cc linux-wireless)
>
> Was 2.6.26 OK?
>

No.  2.6.26 It was actually a little worse, and the git6 was an
improvement since I was at least able to get past DHCP and obtain an
address, after which is died.  The failure is the driver stops receiving
packets, and if you rmmod/modprobe (reload) the driver , then it will work
again and lock up immediately following 'dhclient <interface>'.   tcpdump
-n -i <if> will work hit or miss before the lockup.

Jeff

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/