All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varsha Rao <rvarsha016@gmail.com>
To: pablo@netfilter.org, netfilter-devel@vger.kernel.org
Subject: [PATCH nft] man: Document nft monitor ruleset.
Date: Mon, 31 Jul 2017 00:26:02 +0530	[thread overview]
Message-ID: <597e2bc6.c667620a.541bd.838b@mx.google.com> (raw)

Add documentation for nft monitor ruleset command.

Signed-off-by: Varsha Rao <rvarsha016@gmail.com>
---
 doc/nft.xml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/doc/nft.xml b/doc/nft.xml
index 9c9192c..4d03a3d 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -4385,7 +4385,7 @@ add rule nat prerouting tcp dport 22 redirect to :2222
 				XML, JSON or native nft format.
 			</para>
 			<para>
-				To filter events related to a concrete object, use one of the keywords 'tables', 'chains', 'sets', 'rules', 'elements'.
+				To filter events related to a concrete object, use one of the keywords 'tables', 'chains', 'sets', 'rules', 'elements'				      , 'ruleset'.
 			</para>
 			<para>
 				To filter events related to a concrete action, use keyword 'new' or 'destroy'.
@@ -4417,6 +4417,12 @@ add rule nat prerouting tcp dport 22 redirect to :2222
 % nft monitor chains
 				</programlisting>
 			</example>
+			<example>
+				<title>Listen to ruleset events such as table, chain, rule, set, counters and quotas, in native nft format</title>
+				<programlisting>
+% nft monitor ruleset
+				</programlisting>
+			</example>
 		</refsect2>
 	</refsect1>
 
-- 
2.9.4


             reply	other threads:[~2017-07-30 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-30 18:56 Varsha Rao [this message]
2017-07-31 17:21 ` [PATCH nft] man: Document nft monitor ruleset Pablo Neira Ayuso

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=597e2bc6.c667620a.541bd.838b@mx.google.com \
    --to=rvarsha016@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.