Re: dynamic wep with mulitple keys

[drago01 <drago01@gmail.com>]

On Mon, May 12, 2008 at 2:07 PM, Tomas Winkler <tomasw@gmail.com> wrote:
>
> On Mon, May 12, 2008 at 2:47 PM, drago01 <drago01@gmail.com> wrote:
>  > On Tue, May 6, 2008 at 2:14 PM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
>  >>
>  >> On Tue, May 6, 2008 at 3:10 PM, drago01 <drago01@gmail.com> wrote:
>  >>  >
>  >>  > On Tue, May 6, 2008 at 9:32 AM, Emmanuel Grumbach
>  <egrumbach@gmail.com> wrote:
>  >>  >  >
>  >>  >  > On Tue, May 6, 2008 at 10:22 AM, drago01 <drago01@gmail.com> wrote:
>  >>  >  >  > On Tue, May 6, 2008 at 8:46 AM, Emmanuel Grumbach
>  <egrumbach@gmail.com> 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...
>  >
>  > This changes fix an important bug that otherwise make the driver
>  > useless in some configurations.
>  > So I think it should be backported to 3945 (even when development is
>  > focused on newer hardware)
>
>  But 3945 uses SW encryption this fix is for HW crypto.

I was talking about this:
"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"
which seemed to work for Volker using swcrypto