From: Patrick McHardy <kaber@trash.net>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: ip_conntrack fails to track Windows Vista TCP connection
Date: Mon, 14 Jun 2010 18:15:18 +0200 [thread overview]
Message-ID: <4C165596.8020700@trash.net> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E70B258E2B3@GVW1118EXC.americas.hpqcorp.net>
Fischer, Anna wrote:
> I am trying to track (and NAT) a TCP connection to a Windows Vista machine using ip_conntrack. However, Vista uses the Nagle algorithm combined with the TCP Delayed ACK mechanism which does not ACK every single packet, and it seems as if the connection tracking module has problems with this. Basically it fails to recognize Delayed ACK packets, and as these are not picked up by the connection tracking module, my NAT function does not work and so packets are not delivered properly because they are not rewritten by ip_nat. I am certain that the problem is the Vista TCP stack and its mechanisms as when I configure my Windows Vista machine with Nagle = off and TCPNODelay = 1, then actually connection tracking works fine. Also, all connections with Linux machines are tracked properly.
>
> Is this a known issue?
You're mentioning ip_conntrack, which is obsoleted for multiple
years now. Which kernel version are you using?
next prev parent reply other threads:[~2010-06-14 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 15:25 ip_conntrack fails to track Windows Vista TCP connection Fischer, Anna
2010-06-14 16:15 ` Patrick McHardy [this message]
2010-06-14 16:34 ` Jan Engelhardt
2010-06-14 17:34 ` Fischer, Anna
2010-06-14 17:43 ` Jan Engelhardt
2010-06-14 18:09 ` Fischer, Anna
2010-06-14 20:07 ` Narendra Choyal
2010-06-15 2:23 ` Patrick McHardy
2010-06-15 16:15 ` Fischer, Anna
2010-06-15 16:20 ` Patrick McHardy
2010-06-15 16:20 ` Patrick McHardy
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=4C165596.8020700@trash.net \
--to=kaber@trash.net \
--cc=anna.fischer@hp.com \
--cc=netfilter-devel@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).