public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Antonio Pérez" <aperlu@telefonica.net>
Cc: Giuliano Pochini <pochini@shiny.it>,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 NAT problem
Date: Thu, 16 Dec 2004 15:41:37 -0500	[thread overview]
Message-ID: <41C1F301.1070403@tmr.com> (raw)
In-Reply-To: <41BE1399.8010300@telefonica.net>

Antonio Pérez wrote:

> add this:
> echo 0 > /proc/sys/net/ipv4/tcp_bic
> echo 0 > /proc/sys/net/ipv4/tcp_ecn
> echo 0 > /proc/sys/net/ipv4/tcp_vegas_conf_avoid

I've seen this and similar advice for other problems, and have disabled 
ecn for several systems with networking ailments myself. Would it be 
better to have some of these off by default rather than have multiple 
versions of these problems appear into the future? Is there some common 
case where these not only work but provide a significant benefit so 
great it justifies being the default?

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  parent reply	other threads:[~2004-12-16 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 20:26 2.6.9 NAT problem Giuliano Pochini
2004-12-13 22:11 ` Antonio Pérez
2004-12-14 21:20   ` Giuliano Pochini
2004-12-16 20:41   ` Bill Davidsen [this message]
2004-12-14  9:31 ` Martin Josefsson
2004-12-14  9:53   ` Giuliano Pochini
2004-12-14 21:26   ` Giuliano Pochini
2004-12-15  6:53     ` Martin Josefsson
2004-12-15 19:18       ` Giuliano Pochini
     [not found] <fa.en17uqu.1r1odgm@ifi.uio.no>
     [not found] ` <fa.b00sk8v.12lus29@ifi.uio.no>
2004-12-21  8:34   ` Bodo Eggert
2004-12-21 16:40     ` Bill Davidsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41C1F301.1070403@tmr.com \
    --to=davidsen@tmr.com \
    --cc=aperlu@telefonica.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pochini@shiny.it \
    /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