Bug 68821 - splittcp with tproxy has issues when timestamp is enabled
Summary: splittcp with tproxy has issues when timestamp is enabled
Status: RESOLVED INVALID
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV4 (show other bugs)
Hardware: All Linux
: P1 high
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-16 13:39 UTC by shailendra7479
Modified: 2014-01-16 22:34 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.2
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description shailendra7479 2014-01-16 13:39:44 UTC 
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
Comment 1 Alan 2014-01-16 22:34:59 UTC 
Please direct general questions rather than bug reports to the netdev@vger.kernel.org mailing list or other forums
Note You need to log in before you can comment on or make changes to this bug.