From: Pete Heist <pete@eventide.io>
To: David Lang <david@lang.hm>
Cc: bkil <bkil.hu+Aq@gmail.com>, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes
Date: Fri, 8 Jun 2018 11:37:56 +0200 [thread overview]
Message-ID: <F025D1C1-A369-4E55-BAB7-E04791EFC555@eventide.io> (raw)
In-Reply-To: <alpine.DEB.2.02.1805301750340.6058@nftneq.ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
> On May 31, 2018, at 2:52 AM, David Lang <david@lang.hm> wrote:
>
> On Sat, 19 May 2018, bkil wrote:
>
>> In reply to this thread:
>> https://lists.bufferbloat.net/pipermail/make-wifi-fast/2018-April/001787.html
>>
>> Sorry for the late response, although I can see from yesterday's
>> SmokePing plots that the issue still prevails.
>>
>> 1.
>> You should definitely not allow rates as low as 1Mb/s considering:
>> * plots of signal vs. rate,
>> * topology of closely packed cabins;
>> * mostly static, noise-free camp ground.
>>
>> Almost all of your clients were able to link with >20Mb/s even at
>> 70-80dBm. Those below were probably just idling. I'd limit the network
>> to 802.11g/n-only, and would even consider disabling all rates below
>> 12Mb/s.
>
> I have been wanting to do this on my APs for Scale (wndr3800 APs with ath9k chipsets) and have been unable to find how to do this on these chipsets.
I also didn’t manage to disable specific MCS rates:
- supported_rates and basic_rate in /etc/config/wireless seem to only affect legacy rates, not ht-mcs-2.4 rates.
- "iw dev wlan0 set bitrates” only sets the transmit rate for the AP
But what I did do at 10:45am today, June 8, was disable 802.11b rates with:
uci set wireless.radio0.legacy_rates=‘0'
uci commit
reboot
So at least the minimum rate should be limited to 6Mbit. We’ll see if this helps in the next few days as the camp fills, and if I hear any complaints:
https://www.drhleny.cz/smokeping/
[-- Attachment #2: Type: text/html, Size: 4858 bytes --]
next prev parent reply other threads:[~2018-06-08 9:37 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 16:03 bkil
2018-05-20 18:56 ` Pete Heist
2018-05-31 0:52 ` David Lang
2018-06-08 9:37 ` Pete Heist [this message]
2018-06-09 15:32 ` bkil
2018-06-13 13:07 ` Pete Heist
2018-06-13 13:24 ` Toke Høiland-Jørgensen
2018-06-13 16:01 ` Pete Heist
2018-06-30 19:14 ` bkil
2018-07-04 21:47 ` Pete Heist
2018-07-05 13:08 ` Toke Høiland-Jørgensen
2018-07-05 17:26 ` Pete Heist
2018-07-05 17:37 ` Toke Høiland-Jørgensen
2018-07-05 18:02 ` Pete Heist
2018-07-05 20:17 ` Jonathan Morton
2018-07-09 2:20 ` Aaron Wood
2018-07-09 5:17 ` Jonathan Morton
2018-07-09 6:27 ` Pete Heist
2018-07-09 12:55 ` Sebastian Moeller
2018-07-09 23:21 ` Pete Heist
2018-07-09 5:13 ` David Lang
2018-07-09 23:33 ` Pete Heist
2018-07-10 0:39 ` Pete Heist
2018-07-10 7:02 ` bkil
2018-06-13 16:30 ` Sebastian Moeller
2018-06-13 17:50 ` Toke Høiland-Jørgensen
[not found] ` <CADuVhRWL2aVjzjfLHg1nPFa8Ae-hWrGrE7Wga4eUKon3oqoTXA@mail.gmail.com>
2018-06-30 19:26 ` bkil
2018-06-30 20:04 ` Jannie Hanekom
-- strict thread matches above, loose matches on Subject: below --
2018-04-24 8:33 Pete Heist
2018-04-24 11:54 ` Toke Høiland-Jørgensen
2018-04-24 13:37 ` Pete Heist
2018-04-24 13:51 ` Toke Høiland-Jørgensen
2018-04-24 14:09 ` Pete Heist
2018-04-24 14:34 ` Toke Høiland-Jørgensen
2018-04-24 19:10 ` Pete Heist
2018-04-24 21:32 ` Toke Høiland-Jørgensen
2018-04-25 6:05 ` Pete Heist
2018-04-25 6:36 ` Sebastian Moeller
2018-04-25 17:17 ` Pete Heist
2018-04-26 0:41 ` David Lang
2018-04-26 19:40 ` Pete Heist
2018-04-26 0:38 ` David Lang
2018-04-26 21:41 ` Pete Heist
2018-04-26 21:44 ` Sebastian Moeller
2018-04-26 21:56 ` Pete Heist
2018-04-26 22:04 ` David Lang
2018-04-26 22:47 ` Pete Heist
2018-04-27 10:15 ` Toke Høiland-Jørgensen
2018-04-27 10:32 ` Pete Heist
2018-04-26 0:35 ` David Lang
2018-04-27 11:42 ` Valent Turkovic
2018-04-27 11:50 ` Pete Heist
2018-04-27 11:59 ` Valent Turkovic
2018-04-27 12:17 ` Pete Heist
2018-04-27 11:47 ` Valent Turkovic
2018-04-27 12:00 ` Pete Heist
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=F025D1C1-A369-4E55-BAB7-E04791EFC555@eventide.io \
--to=pete@eventide.io \
--cc=bkil.hu+Aq@gmail.com \
--cc=david@lang.hm \
--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