From: Patrick McHardy <kaber@trash.net>
To: "Christoph A." <casmls@gmail.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: nftables: logging
Date: Thu, 30 Jul 2009 14:42:14 +0200 [thread overview]
Message-ID: <4A719526.5060508@trash.net> (raw)
In-Reply-To: <4A70C3D1.7040809@gmail.com>
Christoph A. wrote:
> from iptables I'm used to see the logging output in the default syslog
> files, with nftables this seams to be different.
> My rule looks like this:
>
> [...]
> ct state new log prefix "start: " accept
>
> but there are no log entries in the syslog file.
> Where does nftables writes its logs?
>
> The nft_log module is loaded:
> lsmod|grep nft_l
> nft_log 1952 1
> nf_tables 25540 43
> nft_meta,nft_log,nft_payload,nft_ct,nft_rbtree,nft_hash,nf_tables_ipv4
>
> For testing it would be very handy to have a working logging setup.
>
> Is there already a way to dump the current rules from the kernel to
> stdout (like iptables -vnL) - if this is even possible?
nftables uses the netfilter logging API, which needs a backend
to actually make something out of the entries. You can either
load ipt_LOG/ip6t_LOG or use nfnetlink_log.
prev parent reply other threads:[~2009-07-30 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 21:49 nftables: logging Christoph A.
2009-07-30 12:42 ` Patrick McHardy [this message]
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=4A719526.5060508@trash.net \
--to=kaber@trash.net \
--cc=casmls@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).