From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.3] 96a75f: Arbitrarily enable ECN on babel packets
Date: Sun, 08 Jul 2012 13:04:15 -0700 [thread overview]
Message-ID: <4ff9e7bfae72_39ff1082af4109373@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.3
Commit: 96a75fc2b8b8b00f4178db375d102c81446ff786
https://github.com/dtaht/ceropackages-3.3/commit/96a75fc2b8b8b00f4178db375d102c81446ff786
Author: Dave Täht <dave.taht@bufferbloat.net>
Date: 2012-07-08 (Sun, 08 Jul 2012)
Changed paths:
A net/quagga/patches/900-Arbitrarily-ECN-enable-babel.patch
Log Message:
-----------
Arbitrarily enable ECN on babel packets
While arguably the wrong thing (babel should do something sane
upon receipt of a ECT(3)) I am trying to analyze the behavior
of the multicast queue which is buried deep in the stack,
far below where it can be seen easily.
It is my intent to monitor codel behavior by (in part) observing
ECT(0) being asserted on babel packets via an ip6tables rule.
In fact I intended to track all sorts of ECN behavior via iptables
rules in the upcoming test series.
Commit: 639d2368bb93a6a5dd38607319b2ab3a1c78e5bb
https://github.com/dtaht/ceropackages-3.3/commit/639d2368bb93a6a5dd38607319b2ab3a1c78e5bb
Author: Dave Täht <dave.taht@bufferbloat.net>
Date: 2012-07-08 (Sun, 08 Jul 2012)
Changed paths:
M net/quagga/Makefile
Log Message:
-----------
quagga: update to head
Compare: https://github.com/dtaht/ceropackages-3.3/compare/b142be518955...639d2368bb93
reply other threads:[~2012-07-08 20:04 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=4ff9e7bfae72_39ff1082af4109373@sh2.rs.github.com.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