From: Florian Westphal <fw@strlen.de>
To: Chris Hall <nftables@gmch.uk>
Cc: netfilter@vger.kernel.org
Subject: Re: Failing to construct a 'set' for TCP Flag filtering.
Date: Thu, 3 Sep 2020 16:24:39 +0200 [thread overview]
Message-ID: <20200903142439.GL7319@breakpoint.cc> (raw)
In-Reply-To: <ae5d9b55-b77d-0a1e-d236-be67eb9333ce@gmch.uk>
Chris Hall <nftables@gmch.uk> wrote:
> On 02/09/2020 18:51, Pablo Neira Ayuso wrote:
> > On Wed, Sep 02, 2020 at 05:44:11PM +0100, Chris Hall wrote:
> >> .... issue with 'add set ip MAIN tcp_good_flags...'
> > > Indeed, nothing seems to work until I 'flush ruleset' again !
> > >
> > > Am I asking for the impossible here ?
>
> > It's a bug, I'll apply this patch to git.
>
> Ah. I'm impressed that it's quickly fixable...
>
> ...but my Fedora appears to be 9 months behind on nftables v0.9.3, so I
> guess I have a bit of a wait :-(
>
> I tried building nftables, but ./configure says:
>
> Package 'libnftnl' has version '1.1.3', required version is '>= 1.1.7'
>
> I tried building and installing libnftnl, which created
> '/usr/local/lib/libnftnl.so.11.3.0'. But that does not seem to satisfy the
> ./configure for nftables ?
It does, but its finding the wrong/old installation, or not searching in
/usr/local.
Try
./configure PKG_CONFIG_PATH=/path/to/where/the/1.1.7.pc-file-is
when building nftables.
find -name '*.pc' /usr/local
might tell you the right directory.
next prev parent reply other threads:[~2020-09-03 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1728814AbgIBQSI/20200902161835Z+839@vger.kernel.org>
2020-09-02 16:44 ` Failing to construct a 'set' for TCP Flag filtering Chris Hall
2020-09-02 17:51 ` Pablo Neira Ayuso
2020-09-03 12:53 ` Chris Hall
2020-09-03 14:24 ` Florian Westphal [this message]
2020-09-03 17:44 ` Chris Hall
2020-09-15 15:43 ` 'meta mark' and 'meta mark set' -- any restrictions on their use ? Chris Hall
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=20200903142439.GL7319@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=nftables@gmch.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.