From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] No 80211n possible with AR9220?
Date: Thu, 01 Apr 2010 22:35:26 -0400 [thread overview]
Message-ID: <1270175726.11685.12.camel@mj> (raw)
In-Reply-To: <4BB218EB.2000301@googlemail.com>
On Tue, 2010-03-30 at 17:29 +0200, Dennis Borgmann wrote:
> # iw dev wlan1 link
> Connected to 00:0e:8e:24:52:2f (on wlan1)
> SSID: testsalat
> freq: 2462
> RX: 40496 bytes (404 packets)
> TX: 3046 bytes (38 packets)
> signal: -48 dBm
> tx bitrate: 1.0 MBit/s
I tried AR9220 on the AP side and AR9280 on the station side.
Everything worked fine with 802.11n. That's what I get on the client:
# iw dev wlan1 link
Connected to 00:26:5a:c2:4c:3d (on wlan1)
SSID: mike2
freq: 2462
RX: 111244 bytes (629 packets)
TX: 20186 bytes (176 packets)
signal: -23 dBm
tx bitrate: 117.0 MBit/s MCS 14
I'm using the current linux-wireless on both sides, so that may be the
reason. I tried channels 6 and 11. I tried no encryption and WPA2 with
CCMP.
I saw the bitrate fall to 1 Mbps if there is no traffic, but it would
immediately return to a high value once I start pinging the AP.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2010-04-02 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 15:29 [ath9k-devel] No 80211n possible with AR9220? Dennis Borgmann
2010-03-30 15:29 ` Dennis Borgmann
2010-04-02 2:35 ` Pavel Roskin [this message]
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=1270175726.11685.12.camel@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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.