From: "Michael K" <micke@klintan.se>
To: netfilter@lists.netfilter.org
Subject: RE: PASV rules opening up my high-ports - Whoops - sent the first one in HTML
Date: Tue, 27 May 2003 00:52:13 +0200 [thread overview]
Message-ID: <002e01c323d9$72974ee0$0200a8c0@klintan.local> (raw)
In-Reply-To: <FKEKLDLBAFLHIMEKAJJAIECJCAAA.jherschel@quarry.com>
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of jherschel
> Sent: Monday, May 26, 2003 10:01 PM
> To: netfilter@lists.netfilter.org
> Subject: PASV rules opening up my high-ports - Whoops - sent
> the first one in HTML
>
>
> Howdy,
>
> Thanks in advance for reading this, if this is a common
> issue, I apologize - but could you point me to a searchable
> archive so I don't bug this list with previously asked questions?
>
> Anyways - here goes .
>
> I've got rules for FTP inbound/outbound for both PORT and
> PASV connections. I'm also running MySQL, which defaults to port 3306.
>
> If FTP PASV rules are enabled, either as a server or client,
> it seems all my high ports are open to be connected to. I've
> tried enforcing state, but I end up either breaking the rule
> so that FTP doesn't work, or I end up opening the high-ports again.
>
> Is there a way to fix this by developing a better rule? Or
> should I limit my PASV ports to a range that does not overlap
> with other services?
>
Something like this
iptables -A INPUT -m state --state ESTABISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m state --state ESTABISHED,RELATED -j ACCEPT
#Passive and active ftp
modprobe ip_conntrack_ftp
#FW to FTP servers
iptables -A OUTPUT -p tcp --dport 21 -j ACCEPT
#FTP Clients to FW
#iptables -A INPUT -p tcp --dport 21 -j ACCEPT
/Klintan
next prev parent reply other threads:[~2003-05-26 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 20:00 PASV rules opening up my high-ports - Whoops - sent the first one in HTML jherschel
2003-05-26 21:33 ` accept local processes Volker Augustin
2003-05-27 15:32 ` Ray Leach
2003-05-26 22:52 ` Michael K [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 21:54 PASV rules opening up my high-ports - Whoops - sent the first one in HTML George Vieira
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='002e01c323d9$72974ee0$0200a8c0@klintan.local' \
--to=micke@klintan.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.