Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Pete Heist <peteheist@gmail.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	cake@lists.bufferbloat.net,
	 make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Cake] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS available
Date: Thu, 16 Feb 2017 08:15:27 -0800	[thread overview]
Message-ID: <CALQXh-OyUu4rSNbLtxiJjY9ZvehP2WiyvKJEwqh+uwgv8-tvDQ@mail.gmail.com> (raw)
In-Reply-To: <B9EF7E2D-A15C-4425-97CA-5E6C02D7111E@gmail.com>

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

The approach that's in all of the Cisco documentation (FWIW) about such
things for wired networks is that the higher-priority traffic classes for
VoIP and video are also bandwidth limited to a fraction of the total (and
less than a majority, at that).  But that's in an environment where you
_can_guarantee a minimum level of service.  With the changing throughput
rates of wifi, that's a bit harder.

But I can certainly see the case being made that the VO and VI queues are
never allowed to be over X% of traffic.

-Aaron

On Thu, Feb 16, 2017 at 1:17 AM, Pete Heist <peteheist@gmail.com> wrote:

>
> > On Feb 16, 2017, at 9:42 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> >
> >> On Feb 16, 2017, at 08:57, Pete Heist <peteheist@gmail.com> wrote:
> >> [… discussion about DSCP to WMM classes mapping]
> >> This always makes me wonder what’s to keep someone from just marking
> all their traffic 0x7 and stomping over everyone else.
> >
> >       I have a gut feeling that an AP in a untrusted/hostile environment
> should monitor the usage of the 4 different WMM classes and step up their
> class accordingly. That is in an environment where there is a lot of AC_VO
> or AC_VI traffic the AP should elevate its normal data packets priority to
> match as not too be drowned out by the other senders. Sort of a reciprocal
> tit-for-tat approach, with the goal that the AP will keep access to a
> decent share of airtime. But since I am a layman in these matters, I might
> be out to lunch on this…
>
> At first I was thinking to just remove diffserv markings entirely, say
> with Cake’s besteffort flag, but I think that “good” and “otherwise
> unknowing” users would suffer, which I think in FreeNet is a vast majority
> of users.
>
> I think the challenge might be what metric to use to know when classes are
> being abused. Maybe roughly if dscp_value * bytes_transferred exceeds some
> threshold in some given period of time, that would work. Best effort
> wouldn’t affect this metric so they can use this class all they want, and
> if someone just uses their connection for typical VoIP usage, the threshold
> shouldn’t be exceeded. Only when a lot of data is transferred per period of
> time in higher classes would they exceed the threshold.
>
> For now, we could just measure this (with iptables?) and send an admin
> email when the threshold is exceeded, then automate a strategy to combat it
> if needed. But I bet most users in a community WISP, if notified, would
> just try to help fix the problem… :)
>
> Pete
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>

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

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

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 21:21 [Make-wifi-fast] " 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
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 [this message]
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=CALQXh-OyUu4rSNbLtxiJjY9ZvehP2WiyvKJEwqh+uwgv8-tvDQ@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=peteheist@gmail.com \
    /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