From: Pablo Neira Ayuso <pablo@netfilter•org>
To: Michal Kubecek <mkubecek@suse•cz>
Cc: netfilter-devel@vger•kernel.org,
Patrick McHardy <kaber@trash•net>,
Jozsef Kadlecsik <kadlec@blackhole•kfki.hu>,
Jonathan Corbet <corbet@lwn•net>,
coreteam@netfilter•org, netdev@vger•kernel.org,
linux-doc@vger•kernel.org, linux-kernel@vger•kernel.org,
bridge@lists•linux-foundation.org
Subject: Re: [PATCH nf-next] netfilter: allow logging from non-init namespaces
Date: Thu, 12 May 2016 11:57:26 +0200 [thread overview]
Message-ID: <20160512095726.GA1975@salvia> (raw)
In-Reply-To: <20160428074838.0BBB5A0C94@unicorn.suse.cz>
Hi Michal,
On Wed, Apr 27, 2016 at 02:48:02PM +0200, Michal Kubecek wrote:
> Commit 69b34fb996b2 ("netfilter: xt_LOG: add net namespace support for
> xt_LOG") disabled logging packets using the LOG target from non-init
> namespaces. The motivation was to prevent containers from flooding
> kernel log of the host. The plan was to keep it that way until syslog
> namespace implementation allows containers to log in a safe way.
>
> However, the work on syslog namespace seems to have hit a dead end
> somewhere in 2013 and there are users who want to use xt_LOG in all
> network namespaces. This patch allows to do so by setting
I understand this stuff is tricky. Did you contact already namespace
folks to see if they plan any move on this?
> /proc/sys/net/netfilter/nf_log_all_netns
My only concern with this is that I don't see how users know what log
message has triggered from what container.
Thanks!
next prev parent reply other threads:[~2016-05-12 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 12:48 [PATCH nf-next] netfilter: allow logging from non-init namespaces Michal Kubecek
2016-05-12 9:57 ` Pablo Neira Ayuso [this message]
2016-05-16 6:43 ` Michal Kubecek
2016-08-16 11:20 ` Michal Kubecek
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=20160512095726.GA1975@salvia \
--to=pablo@netfilter$(echo .)org \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=corbet@lwn$(echo .)net \
--cc=coreteam@netfilter$(echo .)org \
--cc=kaber@trash$(echo .)net \
--cc=kadlec@blackhole$(echo .)kfki.hu \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mkubecek@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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