From: "Aaron Gray" <angray@beeb.net>
To: netfilter@lists.netfilter.org
Subject: Re: Can I use ip_conntrack_ftp on a server firewall ?
Date: Sun, 18 Dec 2005 17:43:30 -0000 [thread overview]
Message-ID: <008001c603fa$919d4bb0$0400a8c0@AMDADVENT> (raw)
In-Reply-To: do34su$1mj$1@sea.gmane.org
>> Okay I have ip_conntrack_ftp loaded in /etc/sysconfig/iptables-config.
>>
>> Still it must require some rules to use it.
>
> Well, you obviously need to allow the initial incoming connection to
> port 21. Beyond that, all you should need are the usual rules to
> allow all ESTABLISHED and RELATED traffic. With the conntrack
> module working, the ftp-data connection will be recognized as
> RELATED. Unless there NAT involved (requiring use of the ip_nat_ftp
> module), it should "just work".
I added a NEW and it now "just works" with Windows Internet Explorer as well
as Unix FTP.
Aaron
prev parent reply other threads:[~2005-12-18 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 23:44 Can I use ip_conntrack_ftp on a server firewall ? Aaron Gray
2005-12-17 4:15 ` Robert Nichols
2005-12-18 2:50 ` Aaron Gray
2005-12-18 7:59 ` Robert Nichols
2005-12-18 17:43 ` Aaron Gray [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='008001c603fa$919d4bb0$0400a8c0@AMDADVENT' \
--to=angray@beeb.net \
--cc=netfilter@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