mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ben@zeus.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Missing ACKs with Linux 2.2/2.4?
Date: Fri, 10 Nov 2000 02:12:01 -0800	[thread overview]
Message-ID: <200011101012.CAA11999@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0011100951300.11412-100000@artemis.cam.zeus.com> (message from Ben Mansell on Fri, 10 Nov 2000 10:13:21 +0000 (GMT))
In-Reply-To: <Pine.LNX.4.30.0011100951300.11412-100000@artemis.cam.zeus.com>

   Date: Fri, 10 Nov 2000 10:13:21 +0000 (GMT)
   From: Ben Mansell <ben@zeus.com>

   This is a resend of the data sent on line 8 of the trace:

   10:10:15.845002 cobalt-box.echo > hydra.3700: P 1:1449(1448) ack 1449 win 31856 <nop,nop,timestamp 0 268081751> (DF)

   It looks like hydra didn't ACK this data, so the server eventually
   re-sent it?

Maybe hydra didn't even receive it. :-)

There are two things to make to solve this riddle.

First, reproduce this as you have been, and afterwards
check if various network error statistic counters have been
incremented.  Here is a short list:

1) On the line from /proc/net/dev for the device used in the
   transfer, any counter other than bytes or packets.

2) From /proc/net/snmp

	Ip: InHdrErrors
	Ip: InDiscards
	Tcp: InErrs

Next, reproduce the problem and trace the session using tcpdump
simultaneously from both sides of the connection.  This will answer
the "did the packets even make it to the other end" questions.

Thanks a lot for helping to hunt this down.

Later,
David S. Miller
davem@redhat.com
-
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:[~2000-11-10 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 19:36 Ben Mansell
2000-11-10  0:20 ` David S. Miller
2000-11-10 10:13   ` Ben Mansell
2000-11-10 10:12     ` David S. Miller [this message]
2000-11-10 11:49       ` Ben Mansell
2000-11-10 11:46         ` David S. Miller
2000-11-10 14:54           ` Ben Mansell
2000-11-10 11:50         ` David S. Miller
2000-11-11 19:26 Bernd Eckenfels
2000-11-11 22:27 ` David S. Miller
2000-11-12 13:30   ` Andi Kleen
2000-11-12 14:26     ` kuznet
     [not found] <20001112163538.A10339@gruyere.muc.suse.de>
2000-11-12 15:59 ` kuznet
2000-11-17  5:36 Bernd Eckenfels
2000-11-17  5:37 Bernd Eckenfels

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=200011101012.CAA11999@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=ben@zeus.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

all inboxes | Powered by JetHome®