Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Joel Newkirk <netfilter@newkirk.us>
To: Aldo Lagana <alagana@discmail.com>, netfilter@lists.netfilter.org
Subject: Re: Filtering in the nat table - opinions wanted
Date: Mon, 24 Mar 2003 17:09:07 -0500	[thread overview]
Message-ID: <200303241709.07575.netfilter@newkirk.us> (raw)
In-Reply-To: <003501c2f232$1c0a5140$6d64a8c0@discmail.com>

On Monday 24 March 2003 01:20 pm, Aldo Lagana wrote:
> by default I set the nat chains (PREROUTING POSTROUTING, etc) to
> ACCEPT.  first off is this bad?
>
> For my web & mail servers using DNAT, I need to add rules - and I do. 
> Same w/ SNAT rules...
>
> The problem has come up with our mail server - we were getting spam
> from one IP address - since my DNAT rule was ACCEPT and forward, the
> mail server kept getting these spam messages.  I stopped the SPAM by
> adding a rule to the beginning of PREROUTING to DROP packets from that
> address.
>
> This made me start thinking - am I doing it right by having all the
> nat chains default ACCEPT?
>
> aldo

Yes.  ACCEPT policy for nat and mangle chains.  You should look to 
setting a DROP policy on FORWARD, though, and ACCEPT only the traffic 
you want to allow through there.  For something like DROPping a specific 
IP, you should have those rules first in FORWARD, followed by the ACCEPT 
rules to let through classes of traffic.  (IE, email connections to and 
from the mail server and ESTABLISHED & RELATED state connections)

If you don't have anything in FORWARD right now, but an ACCEPT policy, 
you should definitely concentrate there.  Start with rules to accept the 
traffic through that you really need, with a LOG rule at the end if the 
chain.  This way everything will still work as it does now, and you can 
check the rules listing to see what rules are matching packets, and 
check the LOG to see what isn't matching any rule.  (and write a rule to 
ACCEPT it if you need it)

j



      parent reply	other threads:[~2003-03-24 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 18:20 Filtering in the nat table - opinions wanted Aldo Lagana
2003-03-24 19:32 ` Kim Jensen
2003-03-24 22:09 ` Joel Newkirk [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=200303241709.07575.netfilter@newkirk.us \
    --to=netfilter@newkirk.us \
    --cc=alagana@discmail.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