From: "John Heffner" <johnwheffner@gmail.com>
To: "Chris Bredesen" <cbredesen@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: Debugging TCP: Treason Uncloaked
Date: Thu, 8 May 2008 11:01:25 -0400 [thread overview]
Message-ID: <1e41a3230805080801hc994773pe0b3d5dadc5b36cb@mail.gmail.com> (raw)
In-Reply-To: <482265A0.8040105@redhat.com>
On Wed, May 7, 2008 at 10:29 PM, Chris Bredesen <cbredesen@redhat.com> wrote:
> Hello,
>
> As per below thread, I'm forwarding to this list/alias. tcpdump output
> is attached to the forum post.
Full binary tcpdumps (including the SYN packets) are more useful.
>From the brief snippet you have, we can't see where the announced
window was reneged, but it's 192.168.1.130 doing it, not the nas box.
You're also getting DSACKs from the nas box, which is also a bit
strange.
Another thing to try is disabling TSO, though I can't think why that
might be causing a problem here.
-John
next prev parent reply other threads:[~2008-05-08 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 2:29 Debugging TCP: Treason Uncloaked Chris Bredesen
2008-05-08 15:01 ` John Heffner [this message]
2008-05-13 11:21 ` Ilpo Järvinen
2008-05-19 16:40 ` Chris Bredesen
2008-05-20 10:17 ` Ilpo Järvinen
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=1e41a3230805080801hc994773pe0b3d5dadc5b36cb@mail.gmail.com \
--to=johnwheffner@gmail.com \
--cc=cbredesen@redhat.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).