From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] ECN on vpns?
Date: Mon, 30 Jun 2014 22:24:23 -0700 [thread overview]
Message-ID: <CAA93jw7VL+tS258oeAP9sL4xJWeTFABgccQ_jjCp0r2RUi=39Q@mail.gmail.com> (raw)
I presently don't have any ipsec based tunnels running (having
reverted to the much easier to setup openvpn), and we'd discussed what
the rfcs said about ecn a while back:
http://permalink.gmane.org/gmane.comp.embedded.cerowrt.devel/470
And I'd noted that encapsulation seemed to be working even further back:
https://lists.bufferbloat.net/pipermail/bloat/2011-June/000554.html
http://huchra.bufferbloat.net/~d/veryhappynetwork.png
but I haven't ever got around to checking what products, if any,
actually decapsulated ECT(1) correctly back into the original IP
header.
Does anyone know if linux + strongswan/libreswan and/or other forms of
vpn encapsulation (tinq, openvpn, commercial products), are doing the
right thing presently? I would figure openvpn can't (due to doing
compression)...
I see ecn negotiation is in the ikev2 standard...
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
reply other threads:[~2014-07-01 5:24 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
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='CAA93jw7VL+tS258oeAP9sL4xJWeTFABgccQ_jjCp0r2RUi=39Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@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