On Fri, May 11, 2012 at 3:40 PM, Jozsef Kadlecsik <kadlec@xxxxxxxxxxxxxxxxx> 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 ...] -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
