From: Noah Causin <n0manletter@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Possible Companion Software for Cake and SQM
Date: Fri, 3 Jun 2016 13:08:20 -0400 [thread overview]
Message-ID: <6f4b3da2-a70d-e713-96b2-f4bb127973b8@gmail.com> (raw)
In-Reply-To: <FE66C2F9-73D2-4413-A263-0E11334520CE@gmail.com>
This would be something that users would deploy. I have read comments
from system administrators of businesses and colleges indicating they
have issues with managing specific applications like Facebook Video, and
this could be a good solution.
I think that this could help a lot of people. Many people who want to
setup QOS on their router want to priority specific applications like
Netflix and Skype. The issue is that many applications use the same
ports, which makes that difficult. Since cake has a robust diffserv
model, I think that a good diffserv-marking DPI solution would work well
with it. OpenWRT doesn't really have one.
I've been really wanting to implement this as an OpenWRT package, but I
lack the expertise.
I was wondering if anyone was interested, maybe they could lend a hand.
Noah
On 6/3/2016 12:20 AM, Jonathan Morton wrote:
>> On 3 Jun, 2016, at 02:39, Noah Causin <n0manletter@gmail.com> wrote:
>>
>> I found this netfilter module that could be useful for traffic shaping with Cake or SQM.
>>
>> https://github.com/betolj/ndpi-netfilter
>>
>> It uses an open source deep packet inspection engine to determine what application a flow is, and it works with iptables. My idea is that this could be used to apply diffserv markings to traffic like Netflix, so that they can be placed into the appropriate classes.
>>
>> iptables -t mangle -A FORWARD -o eth2 -m ndpi --netflix -j DSCP --set-dscp-class cs2
>>
>> What do you think?
> I think this has the potential to be a major CPU hog. That’s a problem on consumer-grade routers.
>
> It’s also not a general solution which can be deployed by ISPs subject to Net Neutrality regulations - because it explicitly works by identifying applications and marking them for discriminatory treatment, which is precisely what Net Neutrality outlaws.
>
> A secondary problem is that iptables currently gets applied *after* the ingress qdisc has finished with the packet. This limits the utility.
>
> - Jonathan Morton
>
prev parent reply other threads:[~2016-06-03 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 23:39 Noah Causin
2016-06-03 4:20 ` Jonathan Morton
2016-06-03 17:08 ` Noah Causin [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f4b3da2-a70d-e713-96b2-f4bb127973b8@gmail.com \
--to=n0manletter@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.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