[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49107543.5080207@blueteddy.net>
Date: Tue, 04 Nov 2008 16:16:03 +0000
From: Dave Hudson <linux-kernel@...eteddy.net>
To: Daniel J Blueman <daniel.blueman@...il.com>
CC: Linux Kernel <linux-kernel@...r.kernel.org>,
Linux Netdev <netdev@...r.kernel.org>,
Linux Networking <linux-net@...r.kernel.org>
Subject: Re: time for TCP ECN defaulting to on?
Daniel J Blueman wrote:
> Is it time to enable TCP ECN per default and get the benefits, since
> router support has been around and known-about for really considerable
> time?
>
> Perhaps it should be a question of enabling it, and educating people
> to disable it if they run into issues, since we'll probably be in the
> same situation in 5 years...and it'll be some time before these
> kernels hit devices/servers anyway.
>
> Daniel
Unfortunately I think you'll find there are sufficiently large numbers
of broken SOHO routers out there that if you try this you'll cause a lot
of problems. The problems range from no connectivity to in a few
extreme cases routers actually crashing or behaving in very
unpredictable ways. Here's one summary that got presented to the IETF
about 18 months ago:
http://www.ietf.org/proceedings/07mar/slides/tsvarea-3/sld6.htm
When a clueless end-user gets a Linux-enabled netbook that crashes their
router while their existing Vista or XP systems appear to work just fine
then the Linux network stack will get the blame for being buggy, not the
router :-(
Regards,
Dave
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists