General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Henrique de Moraes Holschuh" <hmh@hmh.eng.br>
To: "Bufferbloat Mainlinglist" <bloat@lists.bufferbloat.net>
Subject: [Bloat] tcp_ecn=2 (server-mode ECN)
Date: Mon, 18 Apr 2011 13:43:48 -0300	[thread overview]
Message-ID: <1303145028.24248.1442482225@webmail.messagingengine.com> (raw)
In-Reply-To: <4DA67BBE.9050606@taht.net>

On Wed, 13 Apr 2011 22:44 -0600, "Dave Taht" <d@taht.net> wrote:
> He'd not noticed the problem because ubuntu 10.4 (at least, he also
> runs bsd) has tcp_ecn=2, which so far as I know "tries" a ECN enabled
> connect then falls back to not using it.

tcp_ecn=2 is "server mode ECN".  It will enable ECN if, and ONLY if, the
other side requests it during the initial TCP handshake.

AFAICT, it effectively disables ECN on all outgoing connections and
enables it on incoming connections should the other host request ECN
(which it won't when it is also running in tcp_ecn=2 mode).

It is also the kernel default, and AFAIK, the default on every 2010+
Linux distro stable releases.

If you want to use ECN, you have to set tcp_ecn=1 in your Linux box when
you're the one originating TCP connections.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


  parent reply	other threads:[~2011-04-18 16:43 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 ` Henrique de Moraes Holschuh [this message]
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

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=1303145028.24248.1442482225@webmail.messagingengine.com \
    --to=hmh@hmh.eng.br \
    --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