From: Shawn Starr <Shawn.Starr@Home.net>
To: miles@megapathdsl.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM]: Strange network problems with 2.4.0 and 3c59x.o
Date: Fri, 12 Jan 2001 17:00:54 -0500 [thread overview]
Message-ID: <3A5F7E96.AA60C7C4@Home.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10101020019010.8957-100000@vaio.greennet> <3A51D40F.48B9ADB9@home.net> <3A5F791F.BCC236C1@Home.net> <3A5F7D2E.87BFC9B@megapathdsl.net>
Oh, hrm.... Guess I shouldn't have turned that on ;)
Sorry. nevermind :)
Miles Lane wrote:
> Make sure your kernel build .config file contains the line:
>
> # CONFIG_INET_ECN is not set
>
> not
>
> CONFIG_INET_ECN=y
>
> Here's what the kernel configuration help has to say:
>
> Explicit Congestion Notification (ECN) allows routers to notify
> clients about network congestion, resulting in fewer dropped packets
> and increased network performance. This option adds ECN support to the
> Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which
> allows ECN support to be disabled at runtime.
>
> 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.
>
> Shawn Starr wrote:
> >
> > Here's something strange that i've been noticing with 2.4.0. Some websites I am
> > unable to access now. For example:
> >
> > http://www.scotiabank.ca/simplify/index.html
>
> <snip>
> -
> 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/
-
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/
next prev parent reply other threads:[~2001-01-12 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10101020019010.8957-100000@vaio.greennet>
[not found] ` <3A51D40F.48B9ADB9@home.net>
2001-01-12 21:37 ` [PROBLEM]: Strange network problems with 2.4.0 and 3c59x.o Shawn Starr
2001-01-12 21:54 ` Miles Lane
2001-01-12 22:00 ` Shawn Starr [this message]
2001-01-12 21:58 ` Matti Aarnio
2001-01-12 22:04 ` Stefan Smietanowski
2001-01-14 1:03 ` Mike A. Harris
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=3A5F7E96.AA60C7C4@Home.net \
--to=shawn.starr@home.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
/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