netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Thomas De Schampheleire <patrickdepinguin@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: iptables: missing connlabel.conf causes unnecessary error messages
Date: Fri, 5 Sep 2014 11:51:37 +0200	[thread overview]
Message-ID: <20140905095137.GC934@breakpoint.cc> (raw)
In-Reply-To: <CAAXf6LVWzjt_becB7dwFNtcevGZn-nsGxACtZHqrv+4MUSsSaA@mail.gmail.com>

Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> On Fri, Sep 5, 2014 at 11:13 AM, Florian Westphal <fw@strlen.de> wrote:
> > Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> >> 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
> >
> > Right, this happens for static builds.
> 
> If with 'static' you mean 'statically linked', then this is not correct.
> My iptables application is dynamically linked:

I meant --enable-static during configure stage.

  reply	other threads:[~2014-09-05  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  8:06 iptables: missing connlabel.conf causes unnecessary error messages Thomas De Schampheleire
2014-09-05  9:13 ` Florian Westphal
2014-09-05  9:47   ` Thomas De Schampheleire
2014-09-05  9:51     ` Florian Westphal [this message]
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=20140905095137.GC934@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=patrickdepinguin@gmail.com \
    /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).