From: drago01 <drago01@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Tomas Winkler" <tomasw@gmail.com>,
"Emmanuel Grumbach" <egrumbach@gmail.com>,
"Volker Braun" <vbraun@physics.upenn.edu>,
"Linux Wireless" <linux-wireless@vger.kernel.org>
Subject: Re: dynamic wep with mulitple keys
Date: Tue, 13 May 2008 11:44:59 +0200 [thread overview]
Message-ID: <f6ca9fed0805130244x648325a3k2ae7b77fa610ca6d@mail.gmail.com> (raw)
In-Reply-To: <1210670668.3646.56.camel@johannes.berg>
On Tue, May 13, 2008 at 11:24 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
> > > SW crypto is handled by mac80211 so I ponder why it works above 4965
> > > and not over 3945 but it has nothing to do with this particular change
> >
> > OK, Johannes any idea why this happens?
>
> I don't even know what happens :)
he ok.
The problem is that when connecting to a dynamic wep network which
uses multiple keys iwl3945 fails to get a dhcp lease. (See
http://marc.info/?l=linux-wireless&m=120699235803881&w=2)
Volker had the same problem with iwl4965. But when turning off
hwcrypto and therefore use the mac80211 code it works for him.
iwl3945 does not use hwcrypto by default (and when I enable it it does
not work either) but fails. Both should be using the same code
(mac80211) but one driver works and the other doesn't which is odd.
next prev parent reply other threads:[~2008-05-13 9:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 16:52 dynamic wep with mulitple keys Volker Braun
2008-04-23 17:15 ` Tomas Winkler
2008-05-05 14:36 ` Emmanuel Grumbach
[not found] ` <8704f27d0805050735s647ac4aaq469630bde6bc341e@mail.gmail.com>
2008-05-05 15:58 ` Volker Braun
2008-05-06 6:46 ` Emmanuel Grumbach
2008-05-06 7:22 ` drago01
2008-05-06 7:32 ` Emmanuel Grumbach
2008-05-06 12:10 ` drago01
2008-05-06 12:14 ` Emmanuel Grumbach
2008-05-12 11:47 ` drago01
2008-05-12 12:07 ` Tomas Winkler
2008-05-12 12:10 ` drago01
2008-05-12 12:22 ` Tomas Winkler
2008-05-12 12:38 ` drago01
2008-05-13 9:24 ` Johannes Berg
2008-05-13 9:44 ` drago01 [this message]
2008-05-13 10:07 ` Johannes Berg
2008-05-13 10:13 ` drago01
2008-05-13 10:18 ` Johannes Berg
2008-05-08 18:31 ` Volker Braun
2008-05-08 18:49 ` Emmanuel Grumbach
2008-05-12 9:13 ` Emmanuel Grumbach
2008-05-12 11:55 ` Emmanuel Grumbach
2008-05-13 13:53 ` Volker Braun
2008-05-13 14:06 ` Emmanuel Grumbach
2008-05-13 14:15 ` Tomas Winkler
2008-05-05 16:04 ` Emmanuel Grumbach
-- strict thread matches above, loose matches on Subject: below --
2008-03-31 19:37 drago01
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6ca9fed0805130244x648325a3k2ae7b77fa610ca6d@mail.gmail.com \
--to=drago01@gmail.com \
--cc=egrumbach@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=vbraun@physics.upenn.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox