Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS available
Date: Thu, 16 Feb 2017 08:57:52 +0100	[thread overview]
Message-ID: <35E83BE1-73D8-4FF9-B2E8-A49073E67EBA@gmail.com> (raw)
In-Reply-To: <d2f998f1-2955-2aae-2286-38807dede5f2@taht.net>

[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]


> On Feb 16, 2017, at 12:03 AM, Dave Täht <dave@taht.net> wrote:
> 
> What I'd done in cerowrt was disable the internal mac80211 QoS
> classifier entirely. (-1 line of code). Another way to do it is to apply
> an iptables rule to wash away all diffserv markings, but I don't care
> for that answer.
> 
> try as I might I cannot remember if this was even possible in hostapd or
> in the mac layer any other way. I'll look this week.

Aha, so since I’m only doing the rrul_be test for now, this won’t matter anyway right? I suppose somewhere diffserv markings are mapped to WMM access categories.

It looks like AirOS has its own mappings: https://help.ubnt.com/hc/en-us/articles/205231750-airMAX-How-is-QoS-and-prioritization-handled-by-airMAX- <https://help.ubnt.com/hc/en-us/articles/205231750-airMAX-How-is-QoS-and-prioritization-handled-by-airMAX->

and there doesn’t look like a practical way to disable it in their UI. So still, for now, disabling WMM is something I can only do in testing.

It looks like FreeNet doesn’t touch diffserv markings in their QoS config, which means they leave it up to AirOS’s mappings above. This always makes me wonder what’s to keep someone from just marking all their traffic 0x7 and stomping over everyone else.

Thanks,
Pete


[-- Attachment #2: Type: text/html, Size: 2059 bytes --]

  reply	other threads:[~2017-02-16  7:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 21:21 Pete Heist
2017-01-30 21:44 ` Toke Høiland-Jørgensen
2017-01-30 22:48   ` Aaron Wood
2017-02-01 14:53     ` Toke Høiland-Jørgensen
2017-01-30 23:21   ` Dave Taht
2017-01-31 16:40     ` Pete Heist
2017-02-14  8:56     ` Pete Heist
2017-02-15 23:03       ` Dave Täht
2017-02-16  7:57         ` Pete Heist [this message]
2017-02-16  8:42           ` [Make-wifi-fast] [Cake] " Sebastian Moeller
2017-02-16  9:17             ` Pete Heist
2017-02-16 16:15               ` Aaron Wood
2017-02-16 16:21                 ` Sebastian Moeller
2017-02-16 16:51                   ` Pete Heist
2017-02-16 17:19                     ` Jonathan Morton
2017-02-16 19:05                       ` Pete Heist
2017-02-16 20:54                         ` Pete Heist
2017-02-16 21:03                       ` Sebastian Moeller
2017-02-17  7:53                         ` Pete Heist
2017-02-17  9:52                           ` Toke Høiland-Jørgensen
2017-02-19 15:25       ` [Make-wifi-fast] " Dave Taht
2017-01-31 15:52   ` Pete Heist
2017-02-01 14:48     ` Toke Høiland-Jørgensen
2017-02-02  8:25       ` Pete Heist
2017-02-07 11:57         ` Toke Høiland-Jørgensen
2017-02-08 15:26           ` Pete Heist
2017-02-08 16:11             ` Toke Høiland-Jørgensen
2017-02-08 16:35               ` Dave Taht
2017-02-08 17:10                 ` Dave Taht
2017-02-08 17:11                   ` Dave Taht
2017-02-09  8:35                 ` Pete Heist
2017-02-09  7:45               ` Pete Heist
2017-02-09 13:51                 ` Toke Høiland-Jørgensen
2017-02-09 14:20                   ` Pete Heist
2017-02-09 14:44                     ` Toke Høiland-Jørgensen
2017-02-10  7:51                       ` Pete Heist
2017-02-08 18:29             ` [Make-wifi-fast] [Cake] " John Yates
2017-01-30 23:55 ` [Make-wifi-fast] " Dave Taht
2017-01-31 16:58   ` 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=35E83BE1-73D8-4FF9-B2E8-A49073E67EBA@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --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