From: Noah Causin <n0manletter@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Cake with Deep Packet Inspection
Date: Thu, 10 Nov 2016 20:55:27 -0500 [thread overview]
Message-ID: <3e5942d2-6d6b-0e01-8aa6-98c3535c26ef@gmail.com> (raw)
I finally got my project working.
I integrated the NDPI Deep Packet Inspection engine into my LEDE build,
so I could prioritize applications using Cake.
http://www.ntop.org/products/deep-packet-inspection/ndpi/
NDPI integrates into IPTables, which allows me to DSCP mark packets.
Cake reads the DiffServ markings and puts the traffic into appropriate
classes.
I found a Makefile which successfully compiles:
https://github.com/981213/lede_src/blob/0d344bc2958838dcbc547a8f0a3d8842e6f6d2f8/package/my_package/ndpi-netfilter/Makefile
The system works very well. Steam traffic is deprioritized to allow
applications like YouTube, Netflix, and Skype to receive higher amounts
of the available bandwidth.
What I do for ingress is bridge two ports on an extra router, enable
bridge firewalling, and create IPTables rules to mark downstream
packets. The router I use is a D-Link DGL-5500, which is comparable to
an Archer C7.
IPv6 support is not available in this netfilter module, but the IPv4
support is great.
Noah Causin
next reply other threads:[~2016-11-11 1:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 1:55 Noah Causin [this message]
2016-11-11 2:06 ` Outback Dingo
2016-11-11 2:42 ` Noah Causin
2016-11-11 2:52 ` Outback Dingo
2016-11-11 4:28 ` Outback Dingo
2016-11-11 13:04 ` Noah Causin
2016-11-11 14:08 ` Outback Dingo
2016-11-11 14:22 ` Noah Causin
2016-11-11 14:56 ` Outback Dingo
2016-11-11 17:38 ` Outback Dingo
2016-11-11 18:36 ` Jonathan Morton
2016-11-12 9:06 ` Outback Dingo
2016-11-12 14:51 ` Jonathan Morton
2016-11-13 8:28 ` Outback Dingo
2017-01-16 19:47 ` Dave Taht
2018-07-30 13:16 ` Outback Dingo
2016-11-11 3:15 ` Konstantin Shalygin
2016-11-11 3:38 ` Noah Causin
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=3e5942d2-6d6b-0e01-8aa6-98c3535c26ef@gmail.com \
--to=n0manletter@gmail.com \
--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