From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Olaf Kirch <okir@suse.de>, Harald Welte <laforge@netfilter.org>,
netfilter-devel@lists.netfilter.org,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: Fw: [Fwd: [Bug 5644] New: NFS v3 TCP 3-way handshake incorrect, iptables blocks access]
Date: Tue, 29 Nov 2005 23:32:45 +0100 [thread overview]
Message-ID: <438CD70D.3030305@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0511291135430.31216@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> Mounting NFS file systems after a (warm) reboot could take a long time if
> firewalling and connection tracking was enabled.
>
> The reason is that the NFS clients tends to use the same ports (800 and
> counting down). Now on reboot, the server would still have a TCB for an
> existing TCP connection client:800 -> server:2049. The client sends a
> SYN from port 800 to server:2049, which elicits an ACK from the server.
> The firewall on the client drops the ACK because (from its point of
> view) the connection is still in half-open state, and it expects to see
> a SYNACK.
>
> The client will eventually time out after several minutes.
>
> The following patch corrects this, by accepting ACKs on half open connections
> as well.
Thanks Jozsef, I'll pass it on to Dave tommorrow.
prev parent reply other threads:[~2005-11-29 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051123.144419.16922351.davem@davemloft.net>
[not found] ` <20051124140827.GH31478@sunbeam.de.gnumonks.org>
[not found] ` <20051124144940.GV25399@suse.de>
[not found] ` <Pine.LNX.4.58.0511250937560.22835@blackhole.kfki.hu>
2005-11-29 10:43 ` Fw: [Fwd: [Bug 5644] New: NFS v3 TCP 3-way handshake incorrect, iptables blocks access] Jozsef Kadlecsik
2005-11-29 22:32 ` Patrick McHardy [this message]
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=438CD70D.3030305@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@netfilter.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=okir@suse.de \
/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).