From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: iptables: missing connlabel.conf causes unnecessary error messages
Date: Fri, 5 Sep 2014 10:06:35 +0200 [thread overview]
Message-ID: <CAAXf6LW4zfxOMeUO4=UPFUX=0VGjLbM_wKhdb3L7DK4SPBmbhg@mail.gmail.com> (raw)
Hi,
Commit http://git.netfilter.org/iptables/commit/?id=51340f7b6a1103b12d86ef488f7140406d80401e
removed the default /etc/xtables/connlabel.conf file distributed with netfilter.
>From this commit onwards, every call to iptables will show the message:
cannot open connlabel.conf, not registering 'connlabel' match: No
such file or directory
Creating an empty connlabel.conf file does not really help, the
message now becomes:
cannot open connlabel.conf, not registering 'connlabel' match: Success
In order to remove the message, we have to specify at least one label,
for example '0 foo'.
I don't think this is correct behavior: even when not using connlabel
at all, iptables will print an error/warning in its default
installation. The only way to remove this warning is to create a dummy
rule.
Moreover, I do not understand the reasoning of the mentioned commit:
what is the problem in respecting sysconfdir? There are so many
applications and libraries that use autoconf and can have
configuration files in a place respecting sysconfdir.
Finally, even if you do not want to provide a default file with the
iptables installation, an empty file (created by the user) should hide
the error message.
What is your view on this?
Thanks,
Thomas
next reply other threads:[~2014-09-05 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 8:06 Thomas De Schampheleire [this message]
2014-09-05 9:13 ` iptables: missing connlabel.conf causes unnecessary error messages Florian Westphal
2014-09-05 9:47 ` Thomas De Schampheleire
2014-09-05 9:51 ` Florian Westphal
2014-09-05 10:11 ` Thomas De Schampheleire
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='CAAXf6LW4zfxOMeUO4=UPFUX=0VGjLbM_wKhdb3L7DK4SPBmbhg@mail.gmail.com' \
--to=patrickdepinguin@gmail.com \
--cc=fw@strlen.de \
--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).