From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 68821] New: splittcp with tproxy has issues when timestamp is enabled
Date: Thu, 16 Jan 2014 09:34:54 -0800 [thread overview]
Message-ID: <20140116093454.3880cb4c@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Thu, 16 Jan 2014 05:39:52 -0800
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 68821] New: splittcp with tproxy has issues when timestamp is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=68821
Bug ID: 68821
Summary: splittcp with tproxy has issues when timestamp is
enabled
Product: Networking
Version: 2.5
Kernel Version: 3.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: shailendra7479@gmail.com
Regression: No
Hi,
I am having an application which does splittcp with transparency. I have a NAT
box which reuses the 5-tuple frequently. Due to this there is a possibility
that some connections with the same tuple go through our splittcp and some may
go directly to the webserver.
Due to this, the webserver is getting confused and not responding with
SYN-ACKs.
Is there a way to enable transparency in TIMESTAMPs when tproxy is involved for
eg., preserve the incoming timestamp in the outgoing SYN.
Shouldn't the kernel be using the client's timestamp in the outgoing SYNs when
transparency is enabled?
Thanks
Shailendra
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2014-01-16 17:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140116093454.3880cb4c@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.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).