Return-path: Received: from fk-out-0910.google.com ([209.85.128.190]:33698 "EHLO fk-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752826AbYEFMOP (ORCPT ); Tue, 6 May 2008 08:14:15 -0400 Received: by fk-out-0910.google.com with SMTP id 18so1138068fkq.5 for ; Tue, 06 May 2008 05:14:13 -0700 (PDT) Message-ID: <8704f27d0805060514i59db36f0t9801fab7543b8655@mail.gmail.com> (sfid-20080506_141327_005663_65AA487B) Date: Tue, 6 May 2008 15:14:13 +0300 From: "Emmanuel Grumbach" To: drago01 Subject: Re: dynamic wep with mulitple keys Cc: "Volker Braun" , "Tomas Winkler" , "Linux Wireless" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <1208969544.3312.5.camel@localhost.localdomain> <1ba2fa240804231015r41e7d7f5ocf7d78af72fb4622@mail.gmail.com> <8704f27d0805050735s647ac4aaq469630bde6bc341e@mail.gmail.com> <1210003121.11809.10.camel@carrot.hep.upenn.edu> <8704f27d0805052346u24954211l6f55513c78205586@mail.gmail.com> <8704f27d0805060032g2312e7dcwc19f382c431e6cd3@mail.gmail.com> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, May 6, 2008 at 3:10 PM, drago01 wrote: > > On Tue, May 6, 2008 at 9:32 AM, Emmanuel Grumbach wrote: > > > > On Tue, May 6, 2008 at 10:22 AM, drago01 wrote: > > > On Tue, May 6, 2008 at 8:46 AM, Emmanuel Grumbach wrote: > > > > > I just tried compat-wireless-2008-05-05, which does contain > > > > > 03dcb07e74a62eec2badb9f6a091790c484f4a6c. No difference: > > > > > > > > > > > > > Thanks for trying this. > > > > Can you try to load the module with swcrypto=1 and try again ? > > > > This disables the HW encryption acceleration. Trying this will allow > > > > to make 100% sure that the bug is in iwlwifi. The bug is likely to be > > > > there, but I think it is worth to make this 100% sure. > > > > > > Well it happens for me with iwl3945 which uses swcrypto by default see: > > > > > > http://marc.info/?l=linux-wireless&m=120699235803881&w=2 > > > > > > > Actually, I made quite a lot of changes in security in iwl4965 that > > are not in iwl3945 so I think it is worth trying with iwl4965 in SW. > > The security code is not the same between 3945 and 4965 > > OK, are you planning to port this changes/fixes to 3945 ? > Well... Low priority... In any case, if it didn't work with SW encryption, this would indicate that the bug is not in iwlwifi -- Emmanuel Grumbach egrumbach@gmail.com