From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neutron Soutmun Subject: Re: [ANNOUNCE] ipset 6.12 released Date: Fri, 11 May 2012 16:00:42 +0700 Message-ID: References: <4FAC3A87.3010500@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Mr Dash Four , netfilter-devel@vger.kernel.org To: Jozsef Kadlecsik Return-path: Received: from mail-pb0-f46.google.com ([209.85.160.46]:34134 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752748Ab2EKJAn (ORCPT ); Fri, 11 May 2012 05:00:43 -0400 Received: by pbbrp8 with SMTP id rp8so3040934pbb.19 for ; Fri, 11 May 2012 02:00:43 -0700 (PDT) In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: On Fri, May 11, 2012 at 3:40 PM, Jozsef Kadlecsik 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 $ git branch experimental/some_ipset_type $ git checkout experimental/some_ipset_type .... $ make [... test ...]