From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Low speeds when AP is very close to stations.
Date: Wed, 07 Mar 2012 17:04:38 -0800 [thread overview]
Message-ID: <4F5805A6.4020107@candelatech.com> (raw)
In-Reply-To: <CAJ-VmokRa0CbgWRBO7tynO_mAB1bVqBm2vb4V2JEcsk==_hLgQ@mail.gmail.com>
On 03/07/2012 05:00 PM, Adrian Chadd wrote:
> On 7 March 2012 13:17, Ben Greear<greearb@candelatech.com> wrote:
>> I put two ath9k (AR9300) nics in one machine, with
>> 6 antenna poking out, and had one NIC be the AP
>> for the other.
>
> How far apart are there?
Well, here's a picture:
http://www.candelatech.com/images/systems/lf0310-back-lo-72dpi.jpg
3 antenna on that pci faceplate are to NIC A, and the right
antenna and ones connected to the case are to NIC B.
>> It works, but I'm seeing lots of CRC errors and station-to-station throughput
>> is only about 5Mbps (one sending to the other).
>
>
>> I tried setting xmit power lower (to 4, for instance), but that
>> doesn't change the behaviour much.
>
> Well, that's still going to be quite powerful. Can you try setting it to 1 or 2?
Sure, will do that tomorrow.
> I wonder what RX attenuation setting(s) are being used. An RSSI of ~22
> is quite strong. It doesn't -seem- strong enough to cause big issues
> though.
How do I figure this out?
> Hm, what about setting tx/rx chainmask to 1 on both sides?
I'm not sure how to do this either..will poke around tomorrow.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2012-03-08 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 21:17 [ath9k-devel] Low speeds when AP is very close to stations Ben Greear
2012-03-08 0:40 ` Ben Greear
2012-03-08 1:00 ` Adrian Chadd
2012-03-08 1:04 ` Ben Greear [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=4F5805A6.4020107@candelatech.com \
--to=greearb@candelatech.com \
--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.