From: raptor <raptor@tvskat.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip_conntrack_ftp
Date: Tue, 11 May 2004 07:09:46 +0000 [thread overview]
Message-ID: <20040511100946.171bd354@bugs> (raw)
In-Reply-To: <20040511012222.6c12892f@vr>
yep my config is very similar i.e. :
iptables -N block
iptables -A block -i $ifInt0 -j ACCEPT
iptables -A block -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A block -j DROP
iptables -A INPUT -i $ifWan0 -j services
iptables -A FORWARD -i $ifWan0 -j services
iptables -A INPUT -j block
iptables -A FORWARD -j block
I added also this (do I really need it in my config I'm allowing everything from inside anyway):
> iptables -A block -m state --state NEW -i ! $ifWan0 -j ACCEPT
after ESTABLISHED,RELATED but still can do active FTP
"services" is for giving access to wellknown services...
I'm not using NAT
On Mon, 10 May 2004 21:37:27 +0100
Andy Furniss <andy.furniss@dsl.pipex.com> wrote:
> raptor wrote:
> > As read here :
> > http://www.sns.ias.edu/~jns/security/iptables/iptables_conntrack.html
> >
> > modprobe ip_conntrack_ftp
> > would give me the ability to use active ftp if I have (pseudo/simplified code)
> >
> > iptables -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
> > iptables -A FORWARD -j DROP
> >
> > but I cant use active ftp, WHAT IS WRONG.. eth0 is the internal interface..
> >
>
> If you are NATing use ip_nat_ftp aswell.
>
> Not sure that that firewall rule is OK - but then I don't know what else
> you have.
>
> My firewall is a direct copy and paste from one of rustys guides - ppp0
> is my external interface -
>
> ## Create chain which blocks new connections, except if coming from inside.
>
> iptables -N block
> iptables -A block -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A block -m state --state NEW -i ! ppp0 -j ACCEPT
> iptables -A block -j DROP
>
> ## Jump to that chain from INPUT and FORWARD chains.
> iptables -A INPUT -j block
> iptables -A FORWARD -j block
>
> Andy.
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-05-11 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 19:45 [LARTC] ip_conntrack_ftp raptor
2004-05-10 20:37 ` Andy Furniss
2004-05-11 7:09 ` raptor [this message]
2004-05-12 7:53 ` Andy Furniss
2004-05-12 12:29 ` raptor
2004-05-13 10:16 ` Andy Furniss
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=20040511100946.171bd354@bugs \
--to=raptor@tvskat.net \
--cc=lartc@vger.kernel.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.