From: Kenneth Kalmer <kenneth.kalmer@gmail.com>
To: aspenbr <aspenbr@yahoo.com.br>
Cc: NetFilter <netfilter@lists.netfilter.org>
Subject: Re: Iptables + ftp ??
Date: Tue, 17 May 2005 22:46:17 +0200 [thread overview]
Message-ID: <fad9d48405051713464517ed9@mail.gmail.com> (raw)
In-Reply-To: <1116359380.1180.10.camel@maclinux.lotus>
# modprobe ip_conntrack_ftp
Do you want to allow FTP going out of the network onto the internet or
FTP traffic into the server connected to the internet, or worse NATted
to an internal host?
On 17 May 2005 16:49:41 -0300, aspenbr <aspenbr@yahoo.com.br> wrote:
> I am with problem, necessary to liberate the connection of my internal
> net for external site of ftp the problem and that the site of ftp
> connects using random doors, it has somebody me of the one tip as I make
> to create a rule to connect with this site of ftp has security, I am
> using iptables. Thanks: -)
>
>
--
Kenneth Kalmer
kenneth.kalmer@gmail.com
http://opensourcery.blogspot.com
prev parent reply other threads:[~2005-05-17 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 19:49 Iptables + ftp ?? aspenbr
2005-05-17 20:46 ` Kenneth Kalmer [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=fad9d48405051713464517ed9@mail.gmail.com \
--to=kenneth.kalmer@gmail.com \
--cc=aspenbr@yahoo.com.br \
--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