On 18 February 2014 02:43, Patrick McHardy <kaber@xxxxxxxxx> wrote: >> >> Its quite simple, the syntax is: >> % nft event <all|table|chain|rule|set> [xml|json] > > So far we're pretty much (except for shortcuts like default "add rule") > following the scheme "nft action object". "event" doesn't fit in this > scheme, so I'd propose to change this to "monitor". Also I guess object > specification could be optional so "all" wouldn't be needed, but that's > not too important. > Ok, so I propose the syntax: % nft monitor [table|chain|rule|set] [new|delete] [xml|json] >> add rule ip6 filter input handle 4 > > No expressions in the output? Why the set caching then? > Well, in this first approach I was unable to achieve that :-( I needed some feedback (this RFC). The intention is of course print out all the expressions. regards. -- Arturo Borrero González -- 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
