From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Ganesan Natarajan <natrajputra@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: filtering in mangle table
Date: Fri, 27 Jul 2007 07:59:56 -0400 [thread overview]
Message-ID: <1185537596.6574.2.camel@localhost> (raw)
In-Reply-To: <dae53550707270302r6887a6a4g3c9ddfd7d070afab@mail.gmail.com>
On Fri, 2007-07-27 at 15:32 +0530, Ganesan Natarajan wrote:
> Hi,
> My requirement is before giving the packets to user space
> application(even before routing) I need to filter the packets. This
> has to be done for all packets irrespective of particular protocol.
>
> so I am using the the mangle table with PREROUTING chain to filter as
> well as to queue the packets using the DROP, QUEUE targets of
> "iptables". But in man pages it is specified that the filter rules
> should not be added into mangle table.
>
> Is there any issues if I proceed with that?
>
> Ganesan
>
We have been doing something very similar in the open source ISCS
network security management project (http://iscs.sourceforge.net).
Although the bulk of the tens of thousands of access control rules we
create for complex internal and micro-perimeter security are added to
our filter table, we handle malicious packet checks (spoofs, ping
floods, malformed packets, etc.) in the mangle table. Seems to be
working fine for us! - John
--
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com
Financially sustainable open source development
http://www.opensourcedevel.com
next prev parent reply other threads:[~2007-07-27 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 10:02 filtering in mangle table Ganesan Natarajan
2007-07-27 11:59 ` John A. Sullivan III [this message]
2007-07-28 10:24 ` Pascal Hambourg
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=1185537596.6574.2.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=natrajputra@gmail.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