From: Shavian Shakes <shavian78@gmail.com>
To: netfilter@lists.netfilter.org
Subject: netfilter logging at the NF_IP_POST_ROUTING hook ?
Date: Mon, 21 Mar 2005 22:49:42 -0800 [thread overview]
Message-ID: <a7243e5e0503212249cd84cdf@mail.gmail.com> (raw)
New to netfilter/iptables. I am writing a small kernel module using
netfilter hooks. For debugging I need to log the packets at the hooks
NF_IP_POST_ROUTING and NF_IP_PRE_ROUTING.
From what I understand, the iptables chains "INPUT" and "OUTPUT" in
the "filter" table are hooked in at NF_IP_LOCAL_IN and NF_IP_LOCAL_OUT
respectively. So if I try to do something like :
iptables -A OUTPUT -j ULOG --ulog-nlgroup 1 --ulog-prefix foo
this will log the packets from the NF_IP_LOCAL_OUT hook. But I would
like to log them from the NF_IP_POST_ROUTING (and NF_IP_PRE_ROUTING
too) hooks. Is there a simple way to achieve this using
iptables/netfilter?
thanks for any help/pointers.
Shavian.
ps: I tried to do this (without fully understanding if it will work ):
iptables -A POSTROUTING -t nat -j ULOG --ulog-nlgroup 1 --ulog-prefix foo
but it didnt..
reply other threads:[~2005-03-22 6:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a7243e5e0503212249cd84cdf@mail.gmail.com \
--to=shavian78@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox