From: Chris Lowth <chris@lowth.com>
To: Gingold Tomasz <tomasz.gingold@siemens.com>,
netfilter-devel@lists.netfilter.org
Subject: Re: Writing new Netfilter Modules
Date: Sun, 26 May 2002 23:08:26 +0100 [thread overview]
Message-ID: <3CF15CDA.6080105@lowth.com> (raw)
In-Reply-To: <6B6D4D4E2ED1D6119DB80000D11D813EB4CA6F@blns203e.bln.icn.siemens.de>
You could try "Rope", which allows modules to be written using a
scripting language that doesnt required kernel development.
You get access to the vast majority of IP/UDP and TCP headers plus the
data payload, conntrack, packet marks and other facilities.
Currently this is for kernel 2.4.x only - 2.6.x will be covered shortly.
Even if your eventual module isnt written in Rope, it does provide a way
of playing with ideas (protyping) in a safe environment before
committing them to C.
http://www.lowth.com/rope
Chris
Gingold Tomasz wrote:
>Hello,
>
>i want to write my own netfilter module. Can anybody tell me how to start?
>Are there any tutorials/documents which could help?
>
>Up to now i have found the "Linux netfilter Hacking HOWTO", especially
>chapter 4 "Information for Programmers.
>Is this the only help i can obtain?
>
>
>Another question:
>I have found on www.netfilter.org <www.netfilter.org> the following statement:
>"netfilter and iptables are building blocks of a framework inside the Linux <http://www.kernel.org/> 2.4.x and 2.6.x kernel"
>Does this mean, that netfilter and iptables are part of the kernel and don´t have to be installed?
>
>thanks for helping
>gingold tomasz
>berlin
>
>
next prev parent reply other threads:[~2002-05-26 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 10:58 Writing new Netfilter Modules Gingold Tomasz
2002-05-26 22:08 ` Chris Lowth [this message]
2005-05-24 11:06 ` Max Kellermann
2005-06-02 17:17 ` Hadrien HAMEL
2005-06-03 8:45 ` Kenneth Porter
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=3CF15CDA.6080105@lowth.com \
--to=chris@lowth.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=tomasz.gingold@siemens.com \
/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.