From: Brian Grossman <brian@SoftHome.net>
To: linux-kernel@vger.kernel.org
Cc: roger@kea.grace.cri.nz
Subject: tcp stalls with 2.4 (but not 2.2)
Date: Mon, 26 Feb 2001 02:22:40 -0700 [thread overview]
Message-ID: <20010226092240.23713.qmail@lindy.softhome.net> (raw)
I'm seeing stalls sending packets to some clients. I see this problem
under 2.4 (2.4.1 and 2.4.1ac17) but not under 2.2.17.
My theory is there is an ICMP black hole between my server and some of its
clients. Is there a tool to pinpoint that black hole if it exists?
Can anyone suggest another cause or a direction for investigation?
Why does this affect 2.4 but not 2.2?
The characteristics I've discovered so far:
From strace of the server process, each write to the network is
preceeded by a select on the output fd. The select waits for a
long time, after which the write succeeds.
The packets are received by the client a couple minutes after my
server sends them.
The clients I have tested with are win98 and winNT.
The router for both 2.4 and 2.2 servers is running 2.2.18 with
ipvs (ipvs-1.0.2-2.2.18).
That router does not block any ICMP.
The behavior occurs on the 2.4 machine whether the packets are
routed directly or are mangled by ipvs.
I've tried the same machine with both 2.4 and 2.2, as well as
another machine with just 2.2. 2.2 works. 2.4 doesn't.
Both of my servers and the router I mentioned have two tulip
network cards.
The clients I've tested with are behind a modem through earthlink.
Another I suspect to have same problem is behind a modem
through Juno.
I've tried adjusting both /proc/sys/net/ipv4/route/min_adv_mss and
/proc/sys/net/ipv4/route/min_pmtu downward. Do these require an
ifconfig down/up to take effect?
Thanks for any help anyone can supply.
Brian
next reply other threads:[~2001-02-26 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 9:22 Brian Grossman [this message]
2001-02-26 16:11 ` tcp stalls with 2.4 (but not 2.2) Jeremy Jackson
2001-02-27 0:34 ` Brian Grossman
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=20010226092240.23713.qmail@lindy.softhome.net \
--to=brian@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roger@kea.grace.cri.nz \
/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;
as well as URLs for NNTP newsgroup(s).