From: Sebastian Gottschall <s.gottschall@newmedia-net.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Dave Taht" <dave.taht@gmail.com>,
"cake@lists.bufferbloat.net >> Cake List"
<cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake in dd-wrt
Date: Wed, 21 Aug 2019 09:30:33 +0200 [thread overview]
Message-ID: <3d3b6b49-6a8a-c645-e26d-999699c13fa1@newmedia-net.de> (raw)
In-Reply-To: <54438C64-C613-438E-9CB9-6C6D0C5EAFA0@gmail.com>
Am 20.08.2019 um 21:07 schrieb Jonathan Morton:
>> On 20 Aug, 2019, at 9:39 pm, Sebastian Gottschall <s.gottschall@newmedia-net.de> wrote:
>>
>> …a heavy bittorrent downloader will still steal the bandwidth of my scp session.
> If you can identify the Bittorrent packets, you can mark them CS1, and switch on Cake's "diffserv3" mode (as it is by default). Then the Bittorrent packets will still be able to use full bandwidth if it's available, but will be limited to 1/16th of the total if there is contention.
we have already priorisation class system in the gui which was used in
the past which offers more classes than offered but this isnt the point
here.
it wont be limited to a 1/16 if we have multiple lan interfaces or
different settings per user (specified by mac or ip/net). so we need a
cake instance for each lan interface but these cake instances dont know
of each other. so each will use the full bandwidth available
its not just about limiting a single service on a single interface. this
isnt a problem
>
> - Jonathan Morton
next prev parent reply other threads:[~2019-08-21 7:31 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 16:33 Dave Taht
2019-08-20 12:08 ` Sebastian Gottschall
2019-08-20 16:24 ` Dave Taht
2019-08-20 16:47 ` Sebastian Gottschall
2019-08-20 16:58 ` Toke Høiland-Jørgensen
2019-08-20 17:29 ` Sebastian Gottschall
2019-08-20 17:47 ` Toke Høiland-Jørgensen
2019-08-20 18:10 ` Sebastian Gottschall
2019-08-20 18:31 ` Toke Høiland-Jørgensen
2019-08-20 18:39 ` Sebastian Gottschall
2019-08-20 18:49 ` Toke Høiland-Jørgensen
2019-08-21 7:25 ` Sebastian Gottschall
2019-08-20 19:07 ` Jonathan Morton
2019-08-20 23:43 ` Dave Taht
2019-08-21 10:21 ` Toke Høiland-Jørgensen
2019-08-21 11:03 ` Sebastian Moeller
2019-08-21 13:10 ` Dave Taht
2019-08-21 14:52 ` Jonathan Morton
2019-08-21 15:42 ` [Cake] pie " Dave Taht
2019-08-21 16:12 ` Sebastian Gottschall
2019-08-21 16:21 ` Sebastian Moeller
2019-08-21 16:28 ` Sebastian Gottschall
2019-08-21 16:50 ` Dave Taht
2019-08-21 21:40 ` Toke Høiland-Jørgensen
2019-08-21 21:53 ` Dave Taht
2019-08-22 9:18 ` Sebastian Gottschall
2019-08-22 13:15 ` [Cake] Wifi Memory limits in small platforms Dave Taht
2019-08-22 14:59 ` Dave Taht
2019-08-22 15:48 ` Sebastian Gottschall
2019-08-22 17:03 ` Dave Taht
2019-08-22 17:37 ` Sebastian Gottschall
2019-08-22 18:23 ` Toke Høiland-Jørgensen
2019-08-22 18:56 ` Dave Taht
2019-08-22 19:37 ` [Cake] [Battlemesh] " Toke Høiland-Jørgensen
2019-08-22 20:10 ` Sebastian Moeller
2019-08-22 20:30 ` [Cake] " Sebastian Gottschall
2019-08-22 23:39 ` Dave Taht
2019-08-23 6:25 ` Sebastian Gottschall
2019-08-23 6:48 ` Sebastian Moeller
2019-08-22 20:32 ` [Cake] fq_codel_fast crash/lockup Sebastian Gottschall
2019-08-21 21:39 ` [Cake] pie in dd-wrt Toke Høiland-Jørgensen
2019-08-22 9:17 ` Sebastian Gottschall
2019-08-22 10:12 ` Toke Høiland-Jørgensen
2019-08-21 7:30 ` Sebastian Gottschall [this message]
2019-08-20 18:05 ` [Cake] cake " Sebastian Gottschall
2019-08-20 23:43 ` Dave Taht
2019-08-20 23:34 ` Dave Taht
2019-08-21 7:44 ` Sebastian Gottschall
2019-08-21 7:44 ` Sebastian Moeller
2019-08-21 7:50 ` Sebastian Gottschall
2019-08-21 7:56 ` Sebastian Moeller
2019-08-21 9:04 ` Sebastian Gottschall
2019-08-21 9:17 ` Sebastian Moeller
2019-08-21 13:20 ` Dave Taht
2019-08-21 16:06 ` Sebastian Gottschall
2019-08-20 18:18 ` Sebastian Gottschall
2019-08-20 23:50 ` Dave Taht
2019-08-21 7:47 ` Sebastian Gottschall
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d3b6b49-6a8a-c645-e26d-999699c13fa1@newmedia-net.de \
--to=s.gottschall@newmedia-net.de \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
--cc=toke@redhat.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