From: "Adam Moffett" <adam@plexicomm.net>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake implementations
Date: Fri, 22 Nov 2019 11:07:54 +0000 [thread overview]
Message-ID: <em348223d0-543c-4b79-ba6b-93f2244326c1@adam-pc> (raw)
In-Reply-To: <CAA93jw4N_-5bui532Ad5QwGn=GH2CnqWYm=BRn75Fgo93R6aJw@mail.gmail.com>
>>
>> Are there any commercial products already using Cake?
>
>Evenroute, eero, ubnt top that list. Evenroute's implementation is
>superb, the first one that used active line measurements to handle
>"sag". Anything derived from openwrt (somewhere between 10-30% of the
>home router market). I'm not sure if preseem is using it or not.
>dd-wrt. Most other things doing "SQM" are doing it via htb + fq_codel.
>
>
An idea which was floated was to experiment with routing ISP customer
traffic through a Linux server using cake to improve customer
experience. Basically like Preseem. My colleague has toyed with it a
bit in small test cases and was impressed with the outcomes.
He's looked closer than I have, but I'm trying to picture how his idea
would scale. I believe I'm seeing a CLI tool for configuring policies.
It seems like we'd have to create a middle layer to create/update
policies for customer's IP address based on information obtained from
our AAA and CRM systems. I can picture some shapes that might take, but
I think it would ultimately have to revolve around scripting the tc
command. There would be thousands of policies and a policy would be
created/updated whenever a subscriber reconnects (e.g. when a DHCP lease
renews or a RADIUS auth event happens or similar).
Should we even pursue this idea?
Although most staff who would touch this will have studied programming
in college, I would not qualify any of us as "programmers" per se. My
biggest concern would be hitting a service affecting problem that we
can't solve.
Second concern is that many of our equipment vendors already use Linux.
Even Cisco now in some products. Maybe we'll waste our time trying to
roll our own solution and then find that a software update from a vendor
next year gives us everything we needed anyway.
-Adam
next prev parent reply other threads:[~2019-11-22 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 21:05 Adam Moffett
2019-11-21 21:53 ` Dave Taht
2019-11-22 11:07 ` Adam Moffett [this message]
2019-11-22 11:46 ` Toke Høiland-Jørgensen
2019-11-22 12:09 ` Justin Kilpatrick
2019-11-22 12:59 ` Toke Høiland-Jørgensen
2019-11-22 13:33 ` Adam Moffett
2019-11-22 14:26 ` Jonathan Morton
2019-11-22 14:33 ` Toke Høiland-Jørgensen
2019-11-22 16:40 ` Jesper Dangaard Brouer
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=em348223d0-543c-4b79-ba6b-93f2244326c1@adam-pc \
--to=adam@plexicomm.net \
--cc=cake@lists.bufferbloat.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