From: "Sumit Pandya" <sumit@elitecore.com>
To: <netfilter-devel@lists.netfilter.org>
Cc: <laforge@netfilter.org>
Subject: Re: Difference between match and target
Date: Wed, 25 Jun 2003 11:59:06 +0530 [thread overview]
Message-ID: <005301c33ae3$141da460$010f430a@elitecore7> (raw)
In-Reply-To: 20030624170402.8564.54425.Mailman@kashyyyk
Hi Harald and All,
Then do Netfilter core team or Netfilter individual module authors will
think of reconsidering this policy? Like ipt_foo and ipt_FOO can be combined
in one kernel module and that module will call both ipt_register_match and
ipt_register_target in MODULE_INIT. In my point of view if we are inserting
2 modules then it is definitely consuming extra (some) memory of kernel.
-- Sumit
> Date: Tue, 24 Jun 2003 18:08:24 +0200
> From: Harald Welte <laforge@netfilter.org>
>
> On Fri, Jun 20, 2003 at 06:33:58PM +0530, Sumit Pandya wrote:
> > What is difference between writing match and target extension for
> > netfilter? Is there something in match which I cannot achieve in target
a=
> nd
> > vice-versa?
>
> From a technical point of view, there is not much differrence.
> There are no technical restrictions, it's a mere policy:
> Matches match against packet data
> Targets connect some action with previously matched packets.
next parent reply other threads:[~2003-06-25 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030624170402.8564.54425.Mailman@kashyyyk>
2003-06-25 6:29 ` Sumit Pandya [this message]
2003-06-25 9:10 ` Difference between match and target Harald Welte
2003-06-27 8:42 ` Andy Whitcroft
[not found] <20030618222710.9325.98884.Mailman@kashyyyk>
2003-06-20 13:03 ` Sumit Pandya
2003-06-24 16:08 ` Harald Welte
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='005301c33ae3$141da460$010f430a@elitecore7' \
--to=sumit@elitecore.com \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@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.