From: Carl Perry <caperry@edolnx.net>
To: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Is IPv4 totally broken in 2.4-test
Date: Mon, 30 Oct 2000 23:53:57 -0600 [thread overview]
Message-ID: <39FE5E75.91BEBD0@edolnx.net> (raw)
In-Reply-To: <39FE5C09.F1B13725@edolnx.net> <200010310404.UAA05392@pizda.ninka.net>
Duh. And here I was thinking that was a good thing. That did it. What exactly
does "Explicit Congestion Notification" do? I figured it was going to put a
message in syslog if the wire is full and packets were being dropped. There
weren't any docs in menuconfig - so I figured "what the hey?". Boy - I was
wrong. Thanks for the quick response. I haven't even gotten the post back yet.
"David S. Miller" wrote:
>
> echo "0" >/proc/sys/net/ipv4/tcp_ecn
>
> Or don't enable CONFIG_INET_ECN in your kernel configuration.
>
> Later,
> David S. Miller
> davem@redhat.com
--
-Carl Perry
caperry@edolnx.net
"Real programmers don't draw flowcharts. Flowcharts are, after
all, the illiterate's form of documentation. Cavemen drew
flowcharts; look how much good it did them."
-Fortune (The App, not the Magazine)
-
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:[~2000-10-31 4:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 5:43 Is IPv4 totally broken in 2.4-test Carl Perry
2000-10-31 4:04 ` David S. Miller
2000-10-31 5:53 ` Carl Perry [this message]
2000-10-31 4:16 ` David S. Miller
2000-10-31 4:36 ` Gregory Maxwell
2000-10-31 4:25 ` Mohammad A. Haque
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=39FE5E75.91BEBD0@edolnx.net \
--to=caperry@edolnx.net \
--cc=davem@redhat.com \
--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