From: Andi Kleen <andi@firstfloor.org>
To: "Karl Pickett" <karl.pickett@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: tcp_tw_recycle broken?
Date: Sat, 15 Nov 2008 14:09:04 +0100 [thread overview]
Message-ID: <874p2916hb.fsf@basil.nowhere.org> (raw)
In-Reply-To: <f9be06770811142329x7d6dcb89vd573962970d503b3@mail.gmail.com> (Karl Pickett's message of "Sat, 15 Nov 2008 02:29:27 -0500")
"Karl Pickett" <karl.pickett@gmail.com> writes:
>
> May I just confirm.. is tcp_tw_reuse NOT dependent on receiving timestamps?
The big problem is that both are incompatible with NAT. So if you
ever talk to any NATed clients don't use it.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-11-15 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 4:37 tcp_tw_recycle broken? Karl Pickett
2008-11-15 5:57 ` Willy Tarreau
2008-11-15 7:29 ` Karl Pickett
2008-11-15 13:09 ` Andi Kleen [this message]
2008-11-15 15:47 ` Karl Pickett
2008-11-15 15:52 ` Willy Tarreau
[not found] ` <f9be06770811142325j79ca0831j7d5820716199811@mail.gmail.com>
2008-11-15 7:45 ` Willy Tarreau
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=874p2916hb.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=karl.pickett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).