From: "Peter Marshall" <peter.marshall@caris.com>
To: Landon Chelf <landonc@starrobbins.com>, netfilter@lists.netfilter.org
Subject: Re: Broken ftp through iptables
Date: Tue, 26 Aug 2003 12:59:32 -0300 [thread overview]
Message-ID: <035b01c36beb$09b417f0$49caa8c0@caris.priv> (raw)
In-Reply-To: 000701c36be5$b629a050$6901a8c0@Station13
If you want to use passive ftp you have to allow stuff destined to port 21
and you also have to allow ( for the commands) traffic to come in on some
port that you don't get to pick. The way to to this without actually
opening a whole bunch of ports is like this
From inside network going out and on forward chain
-p tcp --dport 21 -j ACCEPT
-p tcp -m state --state RELATED - j ACCEPT
FROM outside network back in on the Forward chain
-p tcp -m state --state ESTABLISHED -j ACCEPT
If you want to do Active ftp .... well .... trust me, you dont want to do
this :)
----- Original Message -----
From: "Landon Chelf" <landonc@starrobbins.com>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, August 26, 2003 12:21 PM
Subject: Broken ftp through iptables
> Hello,
>
> I've ran into a recent problem both on rh8 and rh9 using iptables. I've
> setup my firewall to drop everything incomming and forward and am only
> allowing certain ports to be open. I've opened ftp (port 21 tcp) and I
> can connect via FTP from one machine and authenticate, but when I issue
> my first command like "ls" for instance the connection locks up and
> won't do anything. Is there a way to fix this?
>
> Landon
>
>
next prev parent reply other threads:[~2003-08-26 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 15:21 Broken ftp through iptables Landon Chelf
2003-08-26 15:59 ` Peter Marshall [this message]
2003-08-26 16:14 ` Landon Chelf
[not found] <3F4B7D1A.2010408@nucdc.org>
2003-08-26 15:42 ` Landon Chelf
2003-08-26 16:05 ` Julian Gomez
2003-08-26 16:18 ` Peter Marshall
2003-08-26 22:29 ` Alistair Tonner
-- strict thread matches above, loose matches on Subject: below --
2003-08-27 2:43 Josh.Berry
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='035b01c36beb$09b417f0$49caa8c0@caris.priv' \
--to=peter.marshall@caris.com \
--cc=landonc@starrobbins.com \
--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