From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@inl.fr>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ULOGD PATCH 1/3] Do not set oob.family in config as it can be found in packet.
Date: Sat, 09 Feb 2008 18:21:29 +0100 [thread overview]
Message-ID: <47ADE119.7070606@netfilter.org> (raw)
In-Reply-To: <1202372541106-git-send-email-eric@inl.fr>
Eric Leblond wrote:
> WHen using NFLOG or ULOG, obb.family (protocol IPv4 or IPv6) has
> to be setup manually in ulogd.conf configuration file. This was
> used to have the BASE filter parse accordingly the packet. This
> patch suppress oob.family as output keys of NFLOG and ULOG and let
> the BASE filter determine the family of the packet by itself (by
> parsing the raw header).
>
> A good side effect is to be able to log in IPv6 and IPv4 in the
> same group. Before that, two loggers have to be setup separatly.
Applied. Thanks Eric.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2008-02-09 17:21 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 [this message]
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 ` [ULOGD PATCH] Document IPv4 and IPv6 logging difference in NFLOG Eric Leblond
2008-02-10 2:06 ` 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=47ADE119.7070606@netfilter.org \
--to=pablo@netfilter.org \
--cc=eric@inl.fr \
--cc=netfilter-devel@vger.kernel.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.