Re: How to best rate limit and employ fq_codel or cake as a small ISP

Jehan Tremback <[email protected]>
Newsgroups org.kernel.vger.lartc
Message-ID <1513708439.3939053.1210316088.21FECAFD@webmail.messagingengine.com>
It's been a while since I did this but I believe that you can have fq_codel as htb subclasses. I once did some experiments where I had fq_codel inside of drr inside of htb. It never went into production but it did seem to work: http://altheamesh.com/blog/dev-update-2/ (scroll down to the "traffic shaping" section).

Also, when experimenting with this stuff, I can heartily recommend CORE, which is a network simulator made by the Navy: http://altheamesh.com/blog/using-core-for-network-simulation/

In the next few weeks I will need to design a TC setup of my own, so I may give your problem a try while I'm in the TC mindset.

-- 
  Jehan Tremback
  [email protected]

On Fri, Dec 15, 2017, at 7:02 AM, Nathanial Byrnes wrote:
> Hi There,
>   I run a small ISP. I am in the process of building out a new
> centralized traffic management system which enforces our bandwidth
> plans. What I am struggling with is if it is possibly to use fq_codel
> or cake within, or perhaps as a subclass of, the rate limited flow of
> a single customer.  For instance, let's assume I have a customer with
> a 10Mbpsx10Mbps data plan (contrived example...). Currently when they
> are consuming the full 10x10 unless their router is employing cake or
> fq_codel, their experience becomes unpleasant. I'd like to be able to
> employ fq_codel or cake on their behalf such that when they are
> hitting their limits (which I am imposing) Their overall experience is
> not terrible. Is this doable on a single system?
> 
>    Thanks in advance,
>    Nate
> --
> To unsubscribe from this list: send the line "unsubscribe lartc" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.