From: Dave Taht <d@taht.net>
To: bloat@lists.bufferbloat.net, Brian Clapper <bmc@ardentex.com>
Subject: [Bloat] ECN blocking router found
Date: Wed, 13 Apr 2011 22:44:46 -0600 [thread overview]
Message-ID: <4DA67BBE.9050606@taht.net> (raw)
In my travels this month I have been testing ECN enablement at homes and
hotels everywhere I go.
Until today, I was able to have the following settings for ECN on my
laptop everywhere I've been.
net.ipv4.tcp_ecn=1
#net.ipv6.tcp_ecn=0
net.ipv4.tcp_sack=1
net.ipv4.tcp_dsack=1
However, I got to visit Brian Clapper [1] (friend/co-author of gnugol)
tonight, and discovered that his fairly recently purchased router, a:
Etherfast Cable/DSL router Model BEFSR41
Firmware version 2.0.0.4
flat out refused to pass ECN enabled connection attempts (returning an
ICMP unreachable message)
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.
I'm bummed that such a recent router doesn't pass ECN, and will look
into the problem further in the morning.
So I think we must use tcp_ecn = 1 to TEST to make sure ECN is being
passed, and tcp_ecn=2 as the default recommendation.
Perhaps we can synthesize TCP streams to more directly test ECN
capability in the future somehow as part of our testing tools. Are there
any tools that synthesize TCP/ip we could use as a starting point?
[1] http://brizzled.clapper.org/
next reply other threads:[~2011-04-15 0:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 4:44 Dave Taht [this message]
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
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=4DA67BBE.9050606@taht.net \
--to=d@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=bmc@ardentex.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