From: Harald Welte <laforge@netfilter.org>
To: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [BUG] active ftp doesn't work since 2.6.9-rc1
Date: Fri, 1 Oct 2004 15:22:48 +0200 [thread overview]
Message-ID: <20041001132248.GG27499@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20041001111201.GA23033@pc11.op.pod.cz>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Fri, Oct 01, 2004 at 01:12:01PM +0200, Vitezslav Samel wrote:
> Hi!
>
> After upgrade to 2.6.9-rc3 on the firewall (with NAT), active ftp stopped
> working. The first kernel, which doesn't work is 2.6.9-rc1.
> Sympotms: passive ftp works O.K., active FTP doesn't open data stream (and in
> logs there entries about invalid packets - using
> iptables ... -m state --state INVALID -j LOG)
I just tried to reproduce the problem. Can you confirm the problem
disappears after executing
echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal
on your NAT box?
> Cheers,
> Vita Samel
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-01 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 11:12 Vitezslav Samel
2004-10-01 13:22 ` Harald Welte [this message]
2004-10-01 14:10 ` Harald Welte
2004-10-01 22:30 ` David S. Miller
2004-10-04 5:00 ` Vitezslav Samel
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=20041001132248.GG27499@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.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
all inboxes | Powered by JetHome®