From: John Heffner <jheffner@psc.edu>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Sebastian Kuzminsky <seb@highlab.com>, netdev@vger.kernel.org
Subject: Re: bug in tcp?
Date: Tue, 17 Apr 2007 00:30:02 -0400 [thread overview]
Message-ID: <46244D4A.2010209@psc.edu> (raw)
In-Reply-To: <20070416163031.6b87764c@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> A guess: maybe something related to a PAWS wraparound problem.
> Does turning off sysctl net.ipv4.tcp_timestamps fix it?
That was my first thought too (aside from netfilter), but a failed PAWS
check should not result in a reset..
-John
next prev parent reply other threads:[~2007-04-17 4:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 22:28 bug in tcp? Sebastian Kuzminsky
2007-04-16 22:50 ` Stephen Hemminger
2007-04-16 23:05 ` Sebastian Kuzminsky
2007-04-16 23:30 ` Stephen Hemminger
2007-04-17 4:19 ` Sebastian Kuzminsky
2007-04-17 4:30 ` John Heffner [this message]
2007-04-17 4:42 ` Sebastian Kuzminsky
2007-04-17 4:44 ` Philip Craig
2007-04-17 5:35 ` Sebastian Kuzminsky
2007-04-17 6:13 ` Philip Craig
2007-04-17 13:56 ` Sebastian Kuzminsky
2007-04-18 0:03 ` Philip Craig
2007-04-23 18:45 ` bug in my understanding (was Re: bug in tcp?) Sebastian Kuzminsky
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=46244D4A.2010209@psc.edu \
--to=jheffner@psc.edu \
--cc=netdev@vger.kernel.org \
--cc=seb@highlab.com \
--cc=shemminger@linux-foundation.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).