From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] 1416c1: Test tc filter based priority sorting for PPPoE en...
Date: Mon, 13 Oct 2014 17:52:38 -0700 [thread overview]
Message-ID: <543c73d62dc27_47a53fc9c50772bc87986@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.10
Commit: 1416c134416b1d7464b0e598dc6c89da7e9c132a
https://github.com/dtaht/ceropackages-3.10/commit/1416c134416b1d7464b0e598dc6c89da7e9c132a
Author: Sebastian Moeller <moeller0@gmx.de>
Date: 2014-10-14 (Tue, 14 Oct 2014)
Changed paths:
M net/sqm-scripts/files/usr/lib/sqm/functions.sh
A net/sqm-scripts/files/usr/lib/sqm/simple_pppoe.qos
A net/sqm-scripts/files/usr/lib/sqm/simple_pppoe.qos.help
Log Message:
-----------
Test tc filter based priority sorting for PPPoE encapsulated traffic
iptables do not have access to inner headers of passing PPPoE
encapsulated packets. Create a special set of tc filters to
inspect the content of PPPoE packets. While work in progress this does allow
to use the SQM router as PPPoE termination pint yet set up SQM on
the ethernet interface instead of the pppoe interface, and yet keep
decent classification intact. Currently classification is only
working for IPv4 egress traffic. WIP...
Commit: 1b2d107032f10bbf77047c1246c93ed46243cca9
https://github.com/dtaht/ceropackages-3.10/commit/1b2d107032f10bbf77047c1246c93ed46243cca9
Author: Sebastian Moeller <moeller0@gmx.de>
Date: 2014-10-14 (Tue, 14 Oct 2014)
Changed paths:
M net/sqm-scripts/files/usr/lib/sqm/simple_pppoe.qos
Log Message:
-----------
Implement initial classification of egress IPv6 PPPoE packets
This change corrects the tc filter mask for the IPv6 Traffic class field
Now egress classification also works for IPv6.
Compare: https://github.com/dtaht/ceropackages-3.10/compare/a72a1316ad5f...1b2d107032f1
reply other threads:[~2014-10-14 0:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543c73d62dc27_47a53fc9c50772bc87986@hookshot-fe2-cp1-prd.iad.github.net.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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