From: Michel Blais <michel@targointernet.com>
To: Mike <mike@surfglobal.net>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Using cake to shape 1000’s of users.
Date: Mon, 16 Jul 2018 15:13:31 -0400 [thread overview]
Message-ID: <CAAWM72W6yas-ngK2wpofE05NPrNEGdO4ZGPXK8ZXdM7VCrzGpw@mail.gmail.com> (raw)
In-Reply-To: <etPan.5b4ce654.55c0341c.3ce@surfglobal.net>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
I asked the same not long ago. It's currently limited to a global speed
shared by all IP address so you must use a veth with cake config by ip
address.
I would like to eventually see a option in cake with src, dst, src-dual and
dst-dual host mode with bandwidith by ip-address and use a veth with
different cake config by package instead of by user. That would be great
for ISP, only an ipset address list by package to manage once the initial
config done.
Currently didn't have time to test a veth by user. It's in my plan but if
you ever try it. I would gladly like to know the result.
---
Cordialement, / With regards,
Michel Blais
Targo communications
2018-07-16 14:39 GMT-04:00 Mike <mike@surfglobal.net>:
> Is it possible to use cake on one server to provide shaping and QOS to
> 1000’s of users through a transparent bridge with various speed plans. I
> know one company is doing it using fq_codel but I have been unable to
> locate any resources on how to get it to work on more than one speed plan.
> Any help would be greatly appreciated.
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
>
[-- Attachment #2: Type: text/html, Size: 2261 bytes --]
next prev parent reply other threads:[~2018-07-16 19:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 18:39 Mike
2018-07-16 19:01 ` Jonathan Morton
2018-07-16 19:13 ` Michel Blais [this message]
2018-07-17 7:24 Felix Resch
2018-07-17 16:59 ` Dave Taht
2018-07-26 15:46 ` Dan Siemon
2018-07-26 15:48 ` Dave Taht
2018-07-26 18:07 ` Dan Siemon
2018-07-28 15:51 ` Dave Taht
2018-07-28 16:11 ` Jonathan Morton
2018-07-28 16:36 ` Dave Taht
2018-07-26 17:42 ` Toke Høiland-Jørgensen
2018-07-26 18:10 ` Dan Siemon
2018-07-26 21:09 ` Toke Høiland-Jørgensen
2018-07-26 21:38 ` Jonathan Morton
2018-07-27 9:25 ` Pete Heist
2018-07-27 14:04 ` Dan Siemon
2018-07-27 18:58 ` Jonathan Morton
2018-07-28 8:56 ` Toke Høiland-Jørgensen
2018-07-28 15:04 ` Dave Taht
2018-07-28 16:19 ` Jonathan Morton
2018-07-28 16:39 ` Dave Taht
2018-07-28 17:01 ` Pete Heist
2018-07-28 17:37 ` Pete Heist
2018-07-28 17:52 ` Dave Taht
2018-07-28 17:56 ` Dave Taht
2018-07-28 18:12 ` Toke Høiland-Jørgensen
2018-07-29 0:17 ` Pete Heist
2018-07-29 19:14 ` Toke Høiland-Jørgensen
2018-07-30 9:14 ` Pete Heist
2018-07-30 10:09 ` Sebastian Moeller
2018-07-30 10:55 ` Toke Høiland-Jørgensen
2018-07-30 11:05 ` Pete Heist
2018-07-30 11:28 ` Toke Høiland-Jørgensen
2018-07-30 22:10 ` Pete Heist
2018-07-30 22:17 ` Toke Høiland-Jørgensen
2018-07-31 7:31 ` Jonathan Morton
2018-07-30 10:55 ` Pete Heist
2018-07-30 11:05 ` Jonathan Morton
2018-07-28 17:53 ` Jonathan Morton
2018-07-28 18:07 ` Dave Taht
2018-07-28 18:17 ` Toke Høiland-Jørgensen
2018-07-29 23:24 ` Dave Taht
2018-08-07 1:46 ` Dan Siemon
2018-07-28 7:18 ` Pete Heist
2018-07-28 8:06 ` Jonathan Morton
2018-07-28 16:41 ` 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/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=CAAWM72W6yas-ngK2wpofE05NPrNEGdO4ZGPXK8ZXdM7VCrzGpw@mail.gmail.com \
--to=michel@targointernet.com \
--cc=cake@lists.bufferbloat.net \
--cc=mike@surfglobal.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