From: Dave Taht <dave@taht.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Pete Heist <peteheist@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] flow isolation for ISPs
Date: Thu, 06 Apr 2017 07:41:37 -0700 [thread overview]
Message-ID: <87fuhloaxq.fsf@nemesis.taht.net> (raw)
In-Reply-To: <87r315r6ty.fsf@alrua-kau> ("Toke \=\?utf-8\?Q\?H\=C3\=B8iland-J\?\= \=\?utf-8\?Q\?\=C3\=B8rgensen\=22's\?\= message of "Thu, 06 Apr 2017 15:42:01 +0200")
If I had a "vision" here, it was to create a more advanced version
of the the ipset facility, where a customer was represented by
all the IP addresses they might have.
Mac addresses might be hard to get at especially if you were
trying to do this at a layer back from the DSLAM or CMTS.
IP 222.22.22.1 -> 1 customer address
IP 222::1/128 -> 1 v6 p2p on the external interface
IP 222::2/128 -> 1 customer router
IP 222:1::/56 -> 1 customer internal delegation
IP 222.22.22.2 -> 2 customer address
IP 222::3/128 -> 2 v6 p2p on the external interface
IP 222::4/128 -> 2 customer router
IP 222:2::/56 -> 2 customer internal delegation
These would all get thrown into one big ipset (and route)
table, and you'd use the index to hand off to a cake-like
qdisc hanging off of something htb-like.
Sadly:
A) Ipset doesn't work this way (you only get matches)
B) Line conditions vary
C) Total throughput possible on the link varies
as a function of the total bandwidth being used.
Who do you throttle when you are out?
PS (this is my first test of switching back to emacs
again to send mail, let me know if it looks funny)
next prev parent reply other threads:[~2017-04-06 14:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 8:27 Pete Heist
2017-04-06 8:39 ` David Lang
2017-04-06 8:48 ` Pete Heist
2017-04-06 8:57 ` Jonathan Morton
2017-04-06 9:04 ` Pete Heist
2017-04-06 10:26 ` Andy Furniss
2017-04-06 9:11 ` Jonathan Morton
2017-04-06 9:26 ` Pete Heist
2017-04-07 8:13 ` Pete Heist
2017-04-07 8:28 ` Jonathan Morton
2017-04-07 9:37 ` Pete Heist
2017-04-07 11:13 ` Sebastian Moeller
2017-04-07 11:42 ` Pete Heist
2017-04-08 6:16 ` Pete Heist
2017-04-07 10:56 ` John Sager
2017-04-06 9:33 ` Toke Høiland-Jørgensen
2017-04-06 10:26 ` Pete Heist
2017-04-06 10:50 ` Toke Høiland-Jørgensen
2017-04-06 11:34 ` Pete Heist
2017-04-06 12:14 ` Toke Høiland-Jørgensen
2017-04-06 13:30 ` Pete Heist
2017-04-06 13:42 ` Toke Høiland-Jørgensen
2017-04-06 13:50 ` Pete Heist
2017-04-06 14:41 ` Dave Taht [this message]
2017-04-06 12:48 ` Andy Furniss
2017-04-06 13:19 Konstantin Shalygin
[not found] <mailman.340.1491486631.3609.cake@lists.bufferbloat.net>
2017-04-06 14:18 ` Pete Heist
2017-04-06 15:41 ` Andy Furniss
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=87fuhloaxq.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=cake@lists.bufferbloat.net \
--cc=peteheist@gmail.com \
--cc=toke@toke.dk \
/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