Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Cc: Lars Nooden <lars.curator@gmail.com>
Subject: Re: REJECT as a default policy
Date: Tue, 12 Jan 2010 08:53:10 +0100	[thread overview]
Message-ID: <4B4C2A66.3070405@chello.at> (raw)
In-Reply-To: <4B4B1339.1040502@gmail.com>

On 11.01.2010 13:02, Lars Nooden wrote:
> I'd like to add the ability to use the REJECT target as a default policy
> to the netfilter / iptables wishlist.
> 
> Using REJECT as a default is currently possible as a kludge a few steps
> would be saved by allowing it as a default policy.  Perhaps that might
> even speed up some filtering in some cases.
> 
> A good (IMHO) discussion of DROP vs REJECT has been written by Peter Benie :
> 	http://www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject
> 


imagine you get scanned / ddosed / synflooded. For every invalid packet
coming in, you send out an icmp packet. Your host and line could get
quite busy with just sending irrelevant responses, making the dos attack
even more successful.

you will not have control over how many (limit) and what type of icmp
error is through'n out (would need new policy handler).


that's why i personally prefer to DROP to untrusted, while placing
REJECT rules with a limit before the drop-policy, to trusted sides.

regards

Mart



      parent reply	other threads:[~2010-01-12  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 12:02 REJECT as a default policy Lars Nooden
2010-01-11 20:12 ` Gary Smith
2010-01-11 22:08   ` Richard Horton
2010-01-11 22:12     ` Gary Smith
2010-01-12 11:21     ` Lars Nooden
     [not found]       ` <4B4C7242.9070403@freemail.hu>
2010-01-12 13:31         ` Lars Nooden
2010-01-12 14:54           ` Mart Frauenlob
2010-01-12  7:53 ` Mart Frauenlob [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=4B4C2A66.3070405@chello.at \
    --to=mart.frauenlob@chello.at \
    --cc=lars.curator@gmail.com \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox