All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Leblond <eric@inl.fr>
To: netfilter-devel@vger.kernel.org
Subject: [ULOGD PATCH 0/3] Protocol auto detection, bugfixes and doc
Date: Thu,  7 Feb 2008 09:22:18 +0100	[thread overview]
Message-ID: <12023725412-git-send-email-eric@inl.fr> (raw)


Hi,

First patch is the most significative. It modify the behaviour of ulogd for
packet based logging. Before the patch, it was necessary to define the type
of IP protocol that will be used in an NFLOG input. A side effect was that
it was impossible to log in a single netlink group for IPv4 and IPv6. This
patch let the BASE filter do this job of finding the protocol.

This patchset also contains two small fixes and/or improvements:
 * A fix of ulogd info option
 * A review of default config file which has been modified to follow the
 latest modifications

             reply	other threads:[~2008-02-07  8:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07  8:22 Eric Leblond [this message]
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       ` [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=12023725412-git-send-email-eric@inl.fr \
    --to=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.