From: Eric Leblond <eric@inl.fr>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, Eric Leblond <eric@inl.fr>
Subject: [ULOGD PATCH] Document IPv4 and IPv6 logging difference in NFLOG
Date: Sun, 10 Feb 2008 00:19:18 +0100 [thread overview]
Message-ID: <12025991581714-git-send-email-eric@inl.fr> (raw)
In-Reply-To: <47ADE654.5080604@netfilter.org>
Hi,
Here's an update of the patch. This patch is usefull if the modification
in r7348 are reverted.
This patch documents difference between IPv4 and IPv6 logging.
Signed-off-by: Eric Leblond <eric@inl.fr>
---
ulogd.conf.in | 17 +++++++++++++----
1 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/ulogd.conf.in b/ulogd.conf.in
index 3fc3a41..6d76909 100644
--- a/ulogd.conf.in
+++ b/ulogd.conf.in
@@ -43,9 +43,12 @@ plugin="@libdir@/ulogd/ulogd_output_LOGEMU.so"
plugin="@libdir@/ulogd/ulogd_output_OPRINT.so"
plugin="@libdir@/ulogd/ulogd_raw2packet_BASE.so"
-# this is a stack for packet-based logging via LOGEMU
+# this is a stack for IPv4 packet-based logging via LOGEMU
#stack=log1:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
+# this is a stack for IPv6 packet-based logging via LOGEMU
+#stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
+
# this is a stack for ULOG packet-based logging via LOGEMU
#stack=ulog1:ULOG,base1:BASE,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU
@@ -55,21 +58,27 @@ plugin="@libdir@/ulogd/ulogd_raw2packet_BASE.so"
# this is a stack for flow-based logging via OPRINT
#stack=ct1:NFCT,op1:OPRINT
-# this is a stack for NFLOG packet logging to MySQL
+# this is a stack for logging packet to MySQL
#stack=log1:NFLOG,base1:BASE,ifi1:IFINDEX,ip2bin1:IP2BIN,mysql1:MYSQL
-# this is a stack for NFLOG packet logging to PGsql
-#stack=log1:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,pgsql1:PGSQL
+# this is a stack for logging IPv6 packet to PGsql after a collect via NFLOG
+#stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,pgsql1:PGSQL
# this is a stack for flow-based logging to MySQL
#stack=ct1:NFCT,ip2bin1:IP2BIN,mysql2:MYSQL
[ct1]
+# IPv4 logging through NFLOG
[log1]
# netlink multicast group (the same as the iptables --nflog-group param)
group=0
+# IPv6 logging through NFLOG
+[log1]
+group=1 # Group has to be different from the one use in log1
+addressfamily=10 # 10 is value of AF_INET6
+
[ulog1]
# netlink multicast group (the same as the iptables --ulog-nlgroup param)
nlgroup=1
--
1.5.2.5
next prev parent reply other threads:[~2008-02-09 23:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 8:22 [ULOGD PATCH 0/3] Protocol auto detection, bugfixes and doc Eric Leblond
2008-02-07 8:22 ` [ULOGD PATCH 1/3] Do not set oob.family in config as it can be found in packet Eric Leblond
2008-02-08 17:49 ` Peter Warasin
2008-02-08 18:59 ` Eric Leblond
2008-02-09 17:21 ` Pablo Neira Ayuso
2008-02-09 18:13 ` Peter Warasin
2008-02-07 8:22 ` [ULOGD PATCH 2/3] Fix ulogd --info when displaying some default value Eric Leblond
2008-02-09 17:22 ` Pablo Neira Ayuso
2008-02-07 8:22 ` [ULOGD PATCH 3/3] Add examples to config file Eric Leblond
2008-02-09 12:45 ` [RESEND PATCH] Improve ulogd.conf.in Eric Leblond
2008-02-09 17:43 ` Pablo Neira Ayuso
2008-02-09 23:19 ` Eric Leblond [this message]
2008-02-10 2:06 ` [ULOGD PATCH] Document IPv4 and IPv6 logging difference in NFLOG Pablo Neira Ayuso
2008-02-09 17:23 ` [ULOGD PATCH 3/3] Add examples to config file 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=12025991581714-git-send-email-eric@inl.fr \
--to=eric@inl.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox