public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Graham Murray <graham@barnowl.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel network problem ?
Date: 05 Jan 2001 19:31:24 +0000	[thread overview]
Message-ID: <m2itntu777.fsf@barnowl.demon.co.uk> (raw)
In-Reply-To: <000d01c07724$8fa531f0$8900030a@nicolasp> <m3elyiroo9.fsf@shookay.e-steel.com>
In-Reply-To: <m3elyiroo9.fsf@shookay.e-steel.com>

Mathieu Chouquet-Stringer <mchouque@e-steel.com> writes:

> Note that, on the Internet, there are many broken firewalls which
> refuse connections from ECN-enabled machines, and it may be a while
> before these firewalls are fixed. Until then, to access a site behind
> such a firewall (some of which are major sites, at the time of this
> writing) you will have to disable this option, either by saying N now
> or by using the sysctl.

As well as this, it might be worthwhile to complain to these
sites. Otherwise if everyone just turns off ECN then those sites which
block it will probably not fix their problem and ECN will not gain
"public" acceptance. It would be great pity if this were to happen as
ECN has the potential (if widely supported) to greatly reduce network
congestion and bandwidth "waste".

Would it perhaps be possible to have ECN enabled but use something
such as IPTables to unset it when connecting to those sites which
reject ECN connections? So that you could define a rule something like

iptables -A OUTPUT -p tcp --syn -d 1.2.3.4 -j unsetecn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-05 19:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 14:34 kernel network problem ? Nicolas Parpandet
2001-01-05 15:42 ` Matti Aarnio
2001-01-05 15:58   ` Nicolas Noble
2001-01-05 15:42 ` Mathieu Chouquet-Stringer
2001-01-05 19:31   ` Graham Murray [this message]
2001-01-05 15:49 ` Nicolas Noble
2001-01-09  9:37   ` Helge Hafting
2001-01-09 13:57     ` Steven N. Hirsch
2001-01-09 13:32       ` Alan Cox
2001-01-09 13:46         ` Gregory Maxwell
2001-01-10  7:55         ` Nicolas Parpandet
2001-01-09 16:06       ` Gerhard Mack
2001-01-05 15:49 ` Richard Rak
2001-01-05 15:55 ` Nicolas Noble
2001-01-05 23:38 ` J Sloan

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=m2itntu777.fsf@barnowl.demon.co.uk \
    --to=graham@barnowl.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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