From: Nivedita Singhvi <firstname.lastname@example.org>
Subject: Re: Client receives TCP packets but does not ACK
Date: Sun, 1 Jul 2001 14:27:00 -0700 (PDT) [thread overview]
Message-ID: <200107012127.OAA13394@eng4.sequent.com> (raw)
> The bad network behavior was due to shared irqs somehow screwing
> things up. This explained most but not all of the problems.
ah, that's why your test pgm succeeded on my systems..
> When I last posted I had a reproducible test case which spewed a bunch
> of packets from a server to a client. The behavior is that the client
> eventually stops ACKing and so the the connection stalls indefinitely.
> packet. I added printk statements for each of these conditions in
> hopes of detecting why the final packet is not acked. I recompiled
> the kernel, and reran the test. The result was that the packet was
> being droped in tcp_rcv_established() due to an invalid checksum. I
In the interests of not having it be so painful to identify the
problem (to this point, i.e. TCP drops due to checksum failures)
the next time around, I'd like to ask:
- Were you seeing any bad csum error messages in /var/log/messages?
i.e. or else was it only TCP?
- Was the stats field /proc/net/snmp/Tcp:InErrs
reflecting those drops?
- What additional logging/stats gathering would have made this
(silent drops due to checksum failures by TCP) easier to detect?
The stat TcpInErrs is updated for most TCP input failures.
So its not obvious (unless youre real familiar with TCP)
that there are checksum failures happening. It actually
includes only these errors:
- checksum failures
- header len problems
- unexpected SYN's
Is this adequate as a diagnostic, or would adding a breakdown
counter(s) for checksum (and other) failures be useful?
At the moment, there is no logging TCP does on a plain vanilla
kernel, you have to recompile the kernel with NETDEBUG in order
to see logged checksum failures, at least at the TCP level.
It would be nice to have people be able to look at a counter or
stat on the fly and tell whether they're having packets silently
dropped due to checksum failures (and other issues) without needing
to recompile the kernel...
I'd appreciate a cc since I'm not subscribed..
next reply other threads:[~2001-07-01 21:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-01 21:27 Nivedita Singhvi [this message]
2001-07-11 3:43 ` Client receives TCP packets but does not ACK Robert Kleemann
[not found] <E15BiHy-0002xCemail@example.com>
2001-06-17 20:21 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-06-15 12:53 Heusden, Folkert van
2001-06-15 18:27 ` Mike Black
2001-06-15 18:39 ` Gérard Roudier
2001-06-15 19:12 ` Alan Cox
2001-06-17 18:17 ` Pavel Machek
2001-06-17 19:32 ` Alan Cox
2001-06-17 19:40 ` Dan Podeanu
[not found] ` <200106172113.f5HLDhJ377473@saturn.cs.uml.edu>
2001-06-17 22:09 ` Dan Podeanu
2001-06-17 22:35 ` dean gaudet
2001-06-18 11:50 ` Jan Hudec
2001-06-18 16:17 ` dean gaudet
2001-06-18 16:48 ` Jonathan Morton
2001-06-18 22:30 ` dean gaudet
2001-06-18 23:43 ` Jonathan Morton
2001-06-19 2:46 ` dean gaudet
2001-06-20 21:01 ` David Schwartz
[not found] <Pine.LNX.firstname.lastname@example.org>
2001-06-13 8:48 ` Andi Kleen
2001-06-13 16:09 ` Robert Kleemann
2001-06-13 0:26 Robert Kleemann
2001-06-15 3:50 ` Robert Kleemann
2001-06-15 12:44 ` Mike Black
2001-06-15 18:29 ` Albert D. Cahalan
2001-06-15 23:10 ` Robert Kleemann
2001-06-16 11:55 ` Mike Black
2001-06-16 23:56 ` Robert Kleemann
2001-06-27 1:04 ` Robert Kleemann
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).