From: Pavel Roskin <proski@gnu.org>
To: dragoran <drago01@gmail.com>
Cc: Larry Finger <larry.finger@lwfinger.net>,
ipw3945-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org
Subject: Re: iwl3945 lists supported rates backwards
Date: Mon, 29 Oct 2007 03:51:21 -0400 [thread overview]
Message-ID: <1193644281.27622.12.camel@dv> (raw)
In-Reply-To: <4719BA96.3010609@gmail.com>
On Sat, 2007-10-20 at 10:21 +0200, dragoran wrote:
> > I don't know why iwl3945 composes the association request on its own
> > and what happens to it later. Besides, mac80211 10.0.0 is something
> > heavily patched by Intel AFAIK. I wanted to test the git version of
> > Intel mac80211, but intellinuxwireless.org appears to be down or
> > unreachable at the moment and I didn't have a recent clone. The
> > kernel mac80211 is definitely not the suspect.
> >
> > I was aware of "error 18", and when I noticed some activity about
> > rates in wireless-2.6/everything, so I decided to see how that problem
> > would be affected.
> >
> does loading the module with disable_hw_scan=1 helps?
Sorry for delay. disable_hw_scan=1 makes no difference for association
requests. However, it has the opposite effect on the probe requests.
With disable_hw_scan=1, probe requests have the same problem as the
association requests, namely they don't have CCK rates in the supported
rates:
IEEE 802.11
Type/Subtype: Probe Request (0x04)
Frame Control: 0x0040 (Normal)
Version: 0
Type: Management frame (0)
Subtype: 4
Flags: 0x0
DS status: Not leaving DS or network is operating in AD-HOC mode (To DS: 0 From DS: 0) (0x00)
.... .0.. = More Fragments: This is the last fragment
.... 0... = Retry: Frame is not being retransmitted
...0 .... = PWR MGT: STA will stay up
..0. .... = More Data: No data buffered
.0.. .... = Protected flag: Data is not protected
0... .... = Order flag: Not strictly ordered
Duration: 0
Destination address: Broadcast (ff:ff:ff:ff:ff:ff)
Source address: IntelCor_c8:77:a3 (00:13:02:c8:77:a3)
BSS Id: Broadcast (ff:ff:ff:ff:ff:ff)
Fragment number: 0
Sequence number: 5
Frame check sequence: 0x53ed0507 [correct]
[Good: True]
[Bad: False]
IEEE 802.11 wireless LAN management frame
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]
What's even worse, the radiotap header (I'm capturing with the current
MadWifi) indicates that the probe request is sent at 6 Mbps. Of course,
the AP doesn't reply, as it's 802.11b only.
Association requests are sent at 5.5 and 6 Mbps. The association
response is sent, but it's still code 18.
I'm using current wireless-2.6/everything now (it identifies itself as
2.6.24-rc1) and the driver from the kernel to avoid any problems with
Intel's mac80211.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-10-29 7:51 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
2007-10-20 5:40 ` Pavel Roskin
2007-10-20 8:21 ` dragoran
2007-10-29 7:51 ` Pavel Roskin [this message]
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=1193644281.27622.12.camel@dv \
--to=proski@gnu.org \
--cc=drago01@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.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.