All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] I cannot disable RTS/CTS on ath9k.
Date: Thu, 04 Sep 2014 14:09:29 -0700	[thread overview]
Message-ID: <5408D509.7010000@candelatech.com> (raw)
In-Reply-To: <CAHNKnsSLmWOeH7i-K1yFESgSU23FwfUv8oTZF-HkW53+8Yn_qg@mail.gmail.com>

On 09/04/2014 01:58 PM, Sergey Ryazanov wrote:
> 2014-09-04 22:59 GMT+04:00 Ben Greear <greearb@candelatech.com>:
>> My setup is thus:
>>
>> ath9k station
>> ath10k AP (RTS not enabled)
>> ath9k monitor (on separate machine)
>>
>> I tried enabling (value 1024) and and also disabling RTS on the station.
>>
>> The station was forced to reconnect after setting the RTS value on
>> the phy.
>>
>> But, we sniff RTS being sent by station regardless of the ath9k settings.
>>
>> I verified RTS configured as requested using 'iw phy phy0 info' and looking
>> for RTS.
>>
>> Is there something else that might cause RTS to be sent even when station
>> is not configured for RTS?
>>
> Rate control module can do this. About a year ago there was a
> discussion of this feature of minstrel.

Thanks, that must be this thread:

http://comments.gmane.org/gmane.linux.kernel.wireless.general/84459

I think that explains much of my confusion.  I too would like a way to
really disable RTS for testing.  On a mostly quiet channel, sending UDP
frames one way, I still see lots of RTS/CTS, which must mean there are
lots of retries (assuming Minstel-HT is cause of this).

Not what I wanted to find at this late date in my release cycle :P

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Sergey Ryazanov <ryazanov.s.a@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: I cannot disable RTS/CTS on ath9k.
Date: Thu, 04 Sep 2014 14:09:29 -0700	[thread overview]
Message-ID: <5408D509.7010000@candelatech.com> (raw)
In-Reply-To: <CAHNKnsSLmWOeH7i-K1yFESgSU23FwfUv8oTZF-HkW53+8Yn_qg@mail.gmail.com>

On 09/04/2014 01:58 PM, Sergey Ryazanov wrote:
> 2014-09-04 22:59 GMT+04:00 Ben Greear <greearb@candelatech.com>:
>> My setup is thus:
>>
>> ath9k station
>> ath10k AP (RTS not enabled)
>> ath9k monitor (on separate machine)
>>
>> I tried enabling (value 1024) and and also disabling RTS on the station.
>>
>> The station was forced to reconnect after setting the RTS value on
>> the phy.
>>
>> But, we sniff RTS being sent by station regardless of the ath9k settings.
>>
>> I verified RTS configured as requested using 'iw phy phy0 info' and looking
>> for RTS.
>>
>> Is there something else that might cause RTS to be sent even when station
>> is not configured for RTS?
>>
> Rate control module can do this. About a year ago there was a
> discussion of this feature of minstrel.

Thanks, that must be this thread:

http://comments.gmane.org/gmane.linux.kernel.wireless.general/84459

I think that explains much of my confusion.  I too would like a way to
really disable RTS for testing.  On a mostly quiet channel, sending UDP
frames one way, I still see lots of RTS/CTS, which must mean there are
lots of retries (assuming Minstel-HT is cause of this).

Not what I wanted to find at this late date in my release cycle :P

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2014-09-04 21:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 18:59 [ath9k-devel] I cannot disable RTS/CTS on ath9k Ben Greear
2014-09-04 18:59 ` Ben Greear
2014-09-04 20:58 ` [ath9k-devel] " Sergey Ryazanov
2014-09-04 20:58   ` Sergey Ryazanov
2014-09-04 21:09   ` Ben Greear [this message]
2014-09-04 21:09     ` Ben Greear
2014-09-05  1:30     ` [ath9k-devel] " Sujith Manoharan
2014-09-05  1:30       ` Sujith Manoharan

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=5408D509.7010000@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.