Linux wireless drivers development
 help / color / mirror / Atom feed
From: drago01 <drago01@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	ipw3945-devel <ipw3945-devel@lists.sourceforge.net>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"Dan Williams" <dcbw@redhat.com>, "Jouni Malinen" <j@w1.fi>
Subject: Re: [ipw3945-devel] dynamic wep with mulitple keys
Date: Tue, 1 Apr 2008 20:49:02 +0200	[thread overview]
Message-ID: <f6ca9fed0804011149wc306716xb49e1f5dc2791f7a@mail.gmail.com> (raw)
In-Reply-To: <1ba2fa240803312253l4595ce43ya3a6812ceb216f12@mail.gmail.com>

On Tue, Apr 1, 2008 at 7:53 AM, Tomas Winkler <tomasw@gmail.com> wrote:
>
> On 3/31/08, drago01 <drago01@gmail.com> wrote:
>  > Hello,
>  >
>  > I noticed that I can connect to some dynamic wep APs fine using
>  > iwl3945 and with other it does not work, while ipw3945 work with all
>  > of them.
>  > Both driver associate fine but iwl3945 never gets an ip from dhcp.
>  > I checked with iwlist key and it seems that this APs are using only
>  > one key with iwl3945 but two with ipw3945.
>  > The APs that work (I recognize them by BSSID) are using only one key
>  > with both drivers.
>  > Does this mean that mac80211/iwl3945 for some reason drops one key or
>  > never sets it?  (broadcast key?)
>  > Any idea how to get more infos to debug this? (Can attach both iwlist
>  > key outputs if this is needed).
>
>  Currently iwl uses cryptom management provided by mac80211, we are
>  preparing patches for using of HW acceleration till now you must look
>  for
>  problems mac80211.

OK, Johannes any idea what it might be?

>  Some log prints will be useful to debug it anyway.

Which kind of logs exactly?
Tried adding debug=0x43fff and no usefull (related) stuff got printed.

(added some CC's)

  reply	other threads:[~2008-04-01 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 19:37 dynamic wep with mulitple keys drago01
2008-04-01  5:53 ` [ipw3945-devel] " Tomas Winkler
2008-04-01 18:49   ` drago01 [this message]
2008-04-01 21:04     ` Tomas Winkler

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=f6ca9fed0804011149wc306716xb49e1f5dc2791f7a@mail.gmail.com \
    --to=drago01@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.com \
    /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