All of lore.kernel.org
 help / color / mirror / Atom feed
From: Menno Smits <menno@netboxblue.com>
To: netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Simulatenous use of LOG and ULOG on 2.6.14
Date: Mon, 07 Nov 2005 16:25:18 +1000	[thread overview]
Message-ID: <436EF34E.2030806@netboxblue.com> (raw)

Hi,

I'm trying to use the LOG and ULOG targets simultaenously on 2.6.14 but 
am having problems. This used to work on previous kernel versions.

The setup is this:

- kernel configured without the new netlink stuff:
# CONFIG_NETFILTER_NETLINK is not set
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_QUEUE=m
# CONFIG_IP_NF_TARGET_NFQUEUE is not set

- a daemon that uses the old ipulog library starts at boot time and is 
fed by several ULOG rules

- if I try and insert a LOG rule the iptables command appears to work 
but no logs go to syslog except the following message:
    ipt_LOG: not logging via system console since somebody else already
    registered for PF_INET

- if I stop the logging daemon, remove the ULOG rules and unload 
ipt_ULOG I can happily insert functional LOG rules again. However I need 
both LOG and ULOG simultaenously.

How do I make this work as before? I need to be able to use both ULOG 
and LOG at the same time. Will it work if enable 
CONFIG_NETFILTER_NETLINK and related options and port the daemon to the 
new libnetfilter_log library? I'd really prefer to not have to touch the 
daemon at this stage but will if that's the only answer.

Regards,
Menno




Scanned by the NetBox from NetBox Blue
(http://netboxblue.com/)

             reply	other threads:[~2005-11-07  6:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  6:25 Menno Smits [this message]
2005-11-12 10:17 ` Simulatenous use of LOG and ULOG on 2.6.14 Harald Welte
2005-11-17 22:23   ` Menno Smits

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=436EF34E.2030806@netboxblue.com \
    --to=menno@netboxblue.com \
    --cc=netfilter-devel@lists.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.