From: Neutron Soutmun <neo.neutron@gmail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Mr Dash Four <mr.dash.four@googlemail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.12 released
Date: Fri, 11 May 2012 16:00:42 +0700 [thread overview]
Message-ID: <CAMQP0skxm5GVYjDjwd7AwcHbNg6w2fZJQOTMKdAz_ZmbtP4FSA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205111034100.20558@blackhole.kfki.hu>
On Fri, May 11, 2012 at 3:40 PM, Jozsef Kadlecsik
<kadlec@blackhole.kfki.hu> wrote:
> On Thu, 10 May 2012, Mr Dash Four wrote:
>
>> > the point of this feature is providing the easy way that the
>> > third-party or the experimental modules
>> > plug into the existing ipset userspace binary without recompile.
>> >
>> > You could build the experimental ipset "FOO" kernel module and build
>> > the shared-lib of "FOO" userspace tool module and
>> > plug into the system without recompile the ipset userspace tool at
>> > all. It's inspired by iptables (kernel/userspace module).
>> >
>> Is there a documentation on how to do that? For example, if I wish to
>> add my own ipset type/matching (as a separate module), where do I start
>> looking?
>
> As documentation, there's nothing yet.
>
> The userspace part of a set type is quite simple: just the
> parsing, printing, dimension, supported families have to be definied.
> The kernel part is, well, another matter. Of course all the existing
> types can be used as examples.
I definitely agree with you, all the existing types can be used as examples.
/me:
$ git clone <ipset>
$ git branch experimental/some_ipset_type
$ git checkout experimental/some_ipset_type
....
$ make
[... test ...]
prev parent reply other threads:[~2012-05-11 9:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 10:18 [ANNOUNCE] ipset 6.12 released Jozsef Kadlecsik
2012-05-10 10:39 ` Jan Engelhardt
2012-05-10 11:17 ` Jozsef Kadlecsik
2012-05-10 11:28 ` Jan Engelhardt
2012-05-10 11:41 ` Jozsef Kadlecsik
2012-05-10 12:12 ` Neutron Soutmun
2012-05-10 15:13 ` Neutron Soutmun
2012-05-10 15:27 ` Jozsef Kadlecsik
2012-05-10 15:52 ` Neutron Soutmun
2012-05-10 16:00 ` Neutron Soutmun
2012-05-10 16:28 ` Neutron Soutmun
2012-05-10 22:00 ` Mr Dash Four
2012-05-11 2:37 ` Neutron Soutmun
2012-05-11 12:45 ` Mr Dash Four
2012-05-11 19:40 ` Jozsef Kadlecsik
2012-05-11 22:58 ` Mr Dash Four
2012-05-11 23:06 ` Jan Engelhardt
2012-05-11 23:20 ` Mr Dash Four
2012-05-11 8:40 ` Jozsef Kadlecsik
2012-05-11 9:00 ` Neutron Soutmun [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=CAMQP0skxm5GVYjDjwd7AwcHbNg6w2fZJQOTMKdAz_ZmbtP4FSA@mail.gmail.com \
--to=neo.neutron@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=mr.dash.four@googlemail.com \
--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).