From: Sven Riedel <sr@securenet.de>
To: netfilter@vger.kernel.org
Subject: Transfer stalls with NAT under 2.6.24.3
Date: Wed, 26 Mar 2008 09:47:39 +0100 [thread overview]
Message-ID: <47EA0DAB.7080205@securenet.de> (raw)
Hi,
I've run into a strange problem where large file transfers start
stalling over a NATed connection. Packet traces reveal that ACK packets
are sometimes not being passed through to the inside (NATed) host, which
results in a transfer stall until a tcp timeout occurrs and the other
side retransmits the ACK.
This only seems to happen if the conntrack table on the firewall already
contains an entry for the same source and destination in TIME_WAIT
state. If no conntrack entries exist for the same source and
destination, the packets flow fine.
The problem seems to be alevated by setting ip_conntrac_tcp_be_liberal
to 1, but this seems to be only a workaround not a real solution.
Scatter gather and tcp segment offloading have been disabled in the
relevant NICs on the firewall during debugging, to make sure this isn't
a hardware issue.
Is this issue known/is there a patch available or would further
information be needed to help debug the problem?
Regards,
Sven
--
sven.riedel@securenet.de
SecureNet GmbH
Intranet & Internet Solutions
Frankfurter Ring 193a
D-80807 München
Tel: +49 89 32133-632
Fax: +49 89 32133-699
Zentrale: -600
www.securenet.de
Sitz der Gesellschaft: München
HRB München 118876
Geschäftsführer: Thomas Schreiber
next reply other threads:[~2008-03-26 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 8:47 Sven Riedel [this message]
2008-03-26 9:24 ` Transfer stalls with NAT under 2.6.24.3 Patrick McHardy
2008-03-26 10:21 ` Sven Riedel
2008-03-26 15:47 ` Patrick McHardy
2008-03-26 18:45 ` Jozsef Kadlecsik
2008-03-26 19:16 ` Krzysztof Oledzki
2008-03-31 6:53 ` Sven Riedel
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=47EA0DAB.7080205@securenet.de \
--to=sr@securenet.de \
--cc=netfilter@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