On Fri, May 11, 2012 at 5:00 AM, Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx> 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? Nothing yet. However I'm working on the "ipset_hash_iplookup" which is proposed to be used with "SETRAWNAT" target. Both are my experimental ipset type and iptables/xtables target respectively. No problems for SETRAWNAT as the iptables/xtables provides the dynamic module loading support already. -- 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
