From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Rick Jones <rick.jones2@hp.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] enabling outgoing tcp-ecn by default for ipv6 links
Date: Thu, 27 Dec 2012 22:25:04 +0100 [thread overview]
Message-ID: <20121227212504.GC20131@order.stressinduktion.org> (raw)
In-Reply-To: <50DCAB3B.5010902@hp.com>
On Thu, Dec 27, 2012 at 12:10:35PM -0800, Rick Jones wrote:
> On 12/26/2012 06:37 PM, Hannes Frederic Sowa wrote:
> >I am thinking about advancing the ipv4/tcp_ecn knob in linux to
> >distinguish between ipv4 and ipv6 transport and enable ecn signaling
> >on outgoing ipv6 connections by default (for me, at least). I am
> >currently doing so with the help of iptables (echo 1 > tcp_ecn and -j
> >ECN --ecn-tcp-remove).
>
> Any particular reason you aren't willing/able to just flip the
> net.ipv4.tcp_ecn sysctl to turn it on for both? FWIW, that is what I
> have done on netperf.org, with an eye towards seeing what ceases
> working. Thusfar things seem OK. At least I've not had anyone contact
> me to say "Hey! Why can't I reach netperf.org!" ...
But ecn is not employed as long as your clients won't signal ecn
support, too. So there is nothing to break.
I have a squid server where I actually needed to disable outgoing ecn
support because of reachability problems to a german university last
year. This seems to be fixed this year (and they have enabled ipv6,
thus supporting my assumption :) ). I suppose there are still many
ecn-blackholes rendering enabling ecn by default unlikely. I am a bit
more confident this could work some day for ipv6.
Greetings,
Hannes
prev parent reply other threads:[~2012-12-27 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 2:37 Hannes Frederic Sowa
2012-12-27 5:04 ` Michael Richardson
2012-12-27 5:53 ` Hannes Frederic Sowa
2012-12-31 17:37 ` Hannes Frederic Sowa
2015-02-27 15:52 ` Richard Scheffenegger
2012-12-27 20:10 ` Rick Jones
2012-12-27 21:25 ` Hannes Frederic Sowa [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=20121227212504.GC20131@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=bloat@lists.bufferbloat.net \
--cc=rick.jones2@hp.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