netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicola Padovano <nicola.padovano@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: register an hook
Date: Sat, 24 Apr 2010 13:39:51 +0200	[thread overview]
Message-ID: <q2yede9a9eb1004240439q6026727dw48cc9900543717ba@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1004231423530.11467@obet.zrqbmnf.qr>

ok jan, thank you! i'm sorry but i'm a very newbie in this field.
anyway i've have some questions.

first of all: if i program a new target i don't have interest in the
management of the hooks? is it right? and why?

second question: when the checkentry function is used?

thank you again :)

On Fri, Apr 23, 2010 at 2:25 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
> On Friday 2010-04-23 12:50, Nicola Padovano wrote:
>
>>what's the difference? what is a target?
>>I'm analyzing the tarpit patch
>>(http://enterprise.bih.harvard.edu/pub/tarpit-updates/tarpit-2.6.29.patch)
>>and i've found only the registration of that target. and so, how it
>>works, if there isn't an hook registration?
>>
>>help me, please :(
>
> Targets are invoked via Xtables which is a hook user.
>
> targets: http://en.wikipedia.org/wiki/Iptables
> tarpit: http://xtables-addons.sf.net/
> and subsequently: http://jengelh.medozas.de/documents/Netfilter_Modules.pdf
>



-- 
Nicola Padovano
e-mail: nicola.padovano@gmail.com
web: http://npadov.blogspot.com/

      reply	other threads:[~2010-04-24 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  8:55 register an hook Nicola Padovano
2010-04-23 10:27 ` Jan Engelhardt
2010-04-23 10:50   ` Nicola Padovano
2010-04-23 12:25     ` Jan Engelhardt
2010-04-24 11:39       ` Nicola Padovano [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=q2yede9a9eb1004240439q6026727dw48cc9900543717ba@mail.gmail.com \
    --to=nicola.padovano@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).