From: Pete Heist <peteheist@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] CTS protection
Date: Wed, 15 Feb 2017 10:27:04 +0100 [thread overview]
Message-ID: <D13FB30E-D1B9-43E2-ADD7-CC7BD8E39E4C@gmail.com> (raw)
Does anyone know how to disable CTS protection in LEDE (rc2)?
I’ve been running into problems in my testing on the OM2P-HS/LEDE where throughput suddenly drops from ~90Mbps to ~60Mbps, and rrul latency skyrockets, even though the signal and MCS level stay the same. I narrowed this down to the bss flag CTS-protection:
# iperf3 throughput: ~90 Mbps
root@om1:~# iw dev wlan0 link
Connected to ac:86:74:26:aa:aa (on wlan0)
...
signal: -46 dBm
tx bitrate: 144.4 MBit/s MCS 15 short GI
bss flags: short-preamble short-slot-time
...
# iperf3 throughput drops to ~60 Mbps
root@om1:~# iw dev wlan0 link
Connected to ac:86:74:26:aa:aa (on wlan0)
…
signal: -46 dBm
tx bitrate: 144.4 MBit/s MCS 15 short GI
bss flags: CTS-protection short-preamble short-slot-time
...
The flag seems to flip on and off when making tiny changes to router placement, or sometimes seemingly randomly. I suspect it may be because of a distant network also on Channel 1 (scan shows it has a signal of -88), because I seem to be avoiding it for now by swapping with my home network and moving to Channel 6. Maybe those tiny router placement changes were making the distant network either visible or not to the router.
So I’d be glad if I could just manually disable CTS protection, when I know I’ve only got a point-to-point connection and any other networks on the same channel are rather distant.
Also, I suppose this is another example of the difficulty of fixed rate limiting, particularly on crowded frequencies.
Pete
reply other threads:[~2017-02-15 9:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D13FB30E-D1B9-43E2-ADD7-CC7BD8E39E4C@gmail.com \
--to=peteheist@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox