From: Matthew Ford <ford@isoc.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Bufferbloat Mainlinglist <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] No ECN marking in IPv6 linux
Date: Fri, 6 May 2011 19:40:41 +0100 [thread overview]
Message-ID: <11823FFA-4018-4FEE-AC41-0F57A9FD88CC@isoc.org> (raw)
In-Reply-To: <1304695674.3066.57.camel@edumazet-laptop>
On 6 May 2011, at 16:27, Eric Dumazet wrote:
> FYI
>
> IPV6 ECN support is buggy on current linux kernels
>
> Fix is on the way, problem spotted by Steinar H. Gunderson
>
> https://bugzilla.kernel.org/show_bug.cgi?id=34322
>
FWIW, Mac OSX has similar behaviour and I filed the bug with Apple in July of last year.
Summary: When ECN is enabled (by setting net.inet.tcp.ecn_initiate_out = 1 and net.inet.tcp.ecn_negotiate_in = 1), the ECN capable-transport (ECT) bit is not set in the IPv6 Traffic Class field when communicating with ECN-enabled hosts.
Steps to Reproduce:
1. Set net.inet.tcp.ecn_initiate_out=1 and net.inet.tcp.ecn_negotiate_in = 1
2. Connect over IPv6 to another similarly ECN-enabled host and transfer some data over TCP (e.g. an HTTP transaction, or FTP transfer).
3. Monitor the connection with your favourite protocol analyser.
4. Observe that the ECN-Echo bits are correctly set in the initial TCP handshake.
5. Observe that the ECT bit is not being set in the IPv6 Traffic Class field in subsequent packets.
Expected Results:
RFC3168 defines ECN for IP. In IPv4 and IPv6, ECN codepoints are specified as bits 6 and 7 of the TOS Byte and Traffic Class Octet respectively. The ECN Capable Transport (ECT) bit should be set after TCP has successfully concluded ECN initialisation.
Actual Results:
ECT is set for IPv4 communications. ECT is not being set for IPv6 communications.
Mat
prev parent reply other threads:[~2011-05-06 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 4:44 [Bloat] ECN blocking router found Dave Taht
2011-04-14 14:43 ` Brian Clapper
2011-04-15 17:40 ` Rui Paulo
2011-04-23 7:43 ` Richard Scheffenegger
2011-04-18 16:43 ` [Bloat] tcp_ecn=2 (server-mode ECN) Henrique de Moraes Holschuh
2011-05-06 15:27 ` [Bloat] No ECN marking in IPv6 linux Eric Dumazet
2011-05-06 18:14 ` Dave Taht
2011-05-06 18:18 ` Jonathan Morton
2011-05-06 19:42 ` Dave Taht
2011-05-09 3:28 ` Dave Taht
2011-05-09 12:11 ` Lars Eggert
2011-05-16 15:09 ` Juliusz Chroboczek
2011-05-06 18:40 ` Matthew Ford [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=11823FFA-4018-4FEE-AC41-0F57A9FD88CC@isoc.org \
--to=ford@isoc.org \
--cc=bloat@lists.bufferbloat.net \
--cc=eric.dumazet@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