From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id BD73A3B29D for ; Thu, 18 Feb 2021 14:55:51 -0500 (EST) Received: by mail-lj1-x22c.google.com with SMTP id g1so1822979ljj.13 for ; Thu, 18 Feb 2021 11:55:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qe8KB2+DvW2giMyXBlBYmPrGltGYRgduS1NojKbJ7IY=; b=D3/7xka1zNYx5Uu1vzkf9eamw0TIgmCKcVwGn6iiD/x32MUEEDSzgE7WWjEtY4vylO bLnN4D0dpfd2SEkje+YKdvMctOIrePigrf3+KIZ7QpnxalRAHsEuldESJ9YGa/zlzbts WgSVdOjAVhQS76IIyc8syJq6iKBEJ/rV7aMcDE2J4eJf89740GVRl0FER3ITnyb5TSmv hE3o9MYTJRTWCb1M6rpTYIZXKGXs1AdRpeIGU58v6r8DKtWalJmlme/bsXNuNBzTe/Do SPy5fk22zRy04IQH0aCYyqThTs6g9i8ckm43n1lQo5Qrvu5G1LDCLu4ENRmJq5QAIgiZ K8JQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Qe8KB2+DvW2giMyXBlBYmPrGltGYRgduS1NojKbJ7IY=; b=EUHP7/uZy98kfBMRMa5pg19LtRWEd3TKSK3KcEuH6E2pTDjCaWq17VCrDztTv8NqiN P660QC6EtLd2nzbZLnSA3W64nnh3H1C/2XZAZcV7ACJqTx3CGUgfG+aQepaI16nsLW4/ Bg3SgyJDL6vOEPTmaAcGPUBEBUEiqICvZSxPuuL5T+ecPli132vV6I13D7KA+OlMp/un N+yYVDnQQx3s8pATBBg8REgModxNikd3M5XpT/JI5z0ZF7Ufs1HkgL2U8DtCaVdXSZxu xsyyY08ThdqXqOx5EVPOLqHI+GpJHBwNfchFihN9aSl2U68X+rd7idfocj+k0jY0saCf s1Mw== X-Gm-Message-State: AOAM5306GUkJ7bhjydfvVXz4FNjdHmrki3Qg5VV9pHJkClP8HT+CsTxU 1Ogzeogv50u8pS+Yi9OX0MeIvHo7VJLvxY561e4= X-Google-Smtp-Source: ABdhPJwOrIq+dKTEekAnwIzZaniQ+BybqZhEJ5NcJepGZmJedZBNCODqrKvbU02WNXVgnxXQesyOc+moLYLAukFu62E= X-Received: by 2002:ac2:4850:: with SMTP id 16mr1103110lfy.493.1613678150630; Thu, 18 Feb 2021 11:55:50 -0800 (PST) MIME-Version: 1.0 References: <87mtw1kx9c.fsf@toke.dk> <87im6pkweq.fsf@toke.dk> In-Reply-To: From: N0man Tech Date: Thu, 18 Feb 2021 14:55:39 -0500 Message-ID: To: Peter Lepeska Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , cake@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="000000000000f340ce05bba1b8fb" Subject: Re: [Cake] Enforcing video quality question X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2021 19:55:52 -0000 --000000000000f340ce05bba1b8fb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Try looking at fireqos, a component of firehol. It can do per-device limits via a config file. The developers provide an OpenWrt package and you can change the default qdisc to Cake and modify Cake settings. On Thu, Feb 18, 2021 at 2:43 PM Peter Lepeska wrote: > Ok that makes sense. I'll do some reading. Thank you! > > On Thu, Feb 18, 2021 at 2:28 PM Toke H=C3=B8iland-J=C3=B8rgensen > wrote: > >> Peter Lepeska writes: >> >> > A user on the OpenWrt forum suggested hashlimit rules supported by >> > iptables. How does that idea sound to you? >> >> That will result in a cliff-edge policer (i.e., as soon as a device goes >> over its limits it will see every packet get dropped). This doesn't >> interact too well with the burstiness of TCP, so you'll likely get >> erratic behaviour of the traffic if you do that. Doing the same thing >> with HTB means the router will queue+shape each class (and with FQ-CoDel >> on the leaves, you'll get a nice AQM behaviour as well), so that will be >> smoother and less prone to bloat :) >> >> -Toke >> > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake > --000000000000f340ce05bba1b8fb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Try looking at fireqos, a component of firehol. It can do= per-device limits via a config file.

The developers provide an OpenWrt package and you can change = the default qdisc to Cake and modify Cake settings.

On Thu, Feb 18, 202= 1 at 2:43 PM Peter Lepeska <bizz= byster@gmail.com> wrote:
= Ok that makes sense. I'll do some reading. Thank you!

On Thu, Feb 18, 20= 21 at 2:28 PM Toke H=C3=B8iland-J=C3=B8rgensen <toke@toke.dk> wrote:
Peter Lepeska <bizzbyster@gmail.com> writes:

> A user on the OpenWrt forum suggested hashlimit rules supported by
> iptables. How does that idea sound to you?

That will result in a cliff-edge policer (i.e., as soon as a device goes over its limits it will see every packet get dropped). This doesn't
interact too well with the burstiness of TCP, so you'll likely get
erratic behaviour of the traffic if you do that. Doing the same thing
with HTB means the router will queue+shape each class (and with FQ-CoDel on the leaves, you'll get a nice AQM behaviour as well), so that will b= e
smoother and less prone to bloat :)

-Toke
_______________________________________________
Cake mailing list
Cake@lists.= bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
--000000000000f340ce05bba1b8fb--