From: Larry Finger <larry.finger@lwfinger.net>
To: Pavel Roskin <proski@gnu.org>
Cc: ipw3945-devel@lists.sourceforge.net, linux-wireless@vger.kernel.org
Subject: Re: iwl3945 lists supported rates backwards
Date: Fri, 19 Oct 2007 17:28:20 -0500 [thread overview]
Message-ID: <47192F84.1020101@lwfinger.net> (raw)
In-Reply-To: <1192832109.19766.14.camel@dv>
Pavel Roskin wrote:
> Hello!
>
> My iwl3945 device cannot associate to Linksys BEFW11S4. The AP reports
> code 18 (unsupported rates).
>
> I tried the current master branch from iwlwifi repository with the
> current wireless-2.6/everything kernel patched by mac80211 10.0.0, and
> it still exhibits the problem.
>
> It turns out the driver sends CCK rates as extended and OFDM rates as
> "non-extended":
>
> Tagged parameters (23 bytes)
> SSID parameter set: "WTEST"
> Tag Number: 0 (SSID parameter set)
> Tag length: 5
> Tag interpretation: WTEST
> Supported Rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
> Tag Number: 1 (Supported Rates)
> Tag length: 8
> Tag interpretation: Supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 [Mbit/sec]
> Extended Supported Rates: 1.0 2.0 5.5 11.0
> Tag Number: 50 (Extended Supported Rates)
> Tag length: 4
> Tag interpretation: Supported rates: 1.0 2.0 5.5 11.0 [Mbit/sec]
>
> The association request captured by WireShark is attached.
>
> I tried swapping WLAN_EID_SUPP_RATES and WLAN_EID_EXT_SUPP_RATES in the
> sources, but it didn't work. Maybe mac80211 rewrites the request, I
> don't know.
>
> Also, iwl3945 refuses to scan more than several times, and the only
> workaround is to reload the module. Maybe the association failure
> triggers that. If it's not a known problem, I can look closer.
Using the latest git pull from Linus, I am able to associate with my BEFW11S4 AP using the b43
driver. The problem is probably not in mac80211.
Larry
next prev parent reply other threads:[~2007-10-19 22:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 22:15 iwl3945 lists supported rates backwards Pavel Roskin
2007-10-19 22:28 ` Larry Finger [this message]
2007-10-20 5:40 ` Pavel Roskin
2007-10-20 8:21 ` dragoran
2007-10-29 7:51 ` Pavel Roskin
2007-10-29 10:50 ` dragoran
2007-10-29 14:26 ` Pavel Roskin
2007-10-29 10:55 ` dragoran
2007-10-29 14:12 ` Johannes Berg
2007-10-29 16:58 ` Pavel Roskin
2007-10-29 17:09 ` Johannes Berg
2007-10-29 18:53 ` dragoran
2007-10-29 20:31 ` [ipw3945-devel] " mabbas
2007-10-30 12:09 ` Johannes Berg
[not found] ` <1ba2fa240710191714j645c8bfp87a2269b9c141c52@mail.gmail.com>
2007-10-20 6:05 ` Pavel Roskin
2007-10-29 7:54 ` Pavel Roskin
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=47192F84.1020101@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.