From: Laurent Bercot <ska-devel@skarnet.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables: nft fails to add rules to chains
Date: Sun, 22 Mar 2015 20:00:37 +0100 [thread overview]
Message-ID: <550F1155.5000501@skarnet.org> (raw)
In-Reply-To: <20150322190033.GA7145@salvia>
On 22/03/2015 20:00, Pablo Neira Ayuso wrote:
> The constructor seems to be ignored with static links, libnftnl needs
> a fix.
OK, I'll try linking dynamically until it's fixed then.
Thank you!
--
Laurent
next prev parent reply other threads:[~2015-03-22 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 20:24 nftables: nft fails to add rules to chains Laurent Bercot
2015-03-21 20:16 ` Laurent Bercot
2015-03-22 18:31 ` Pablo Neira Ayuso
2015-03-22 18:45 ` Laurent Bercot
2015-03-22 18:47 ` Laurent Bercot
2015-03-22 19:00 ` Pablo Neira Ayuso
2015-03-22 19:00 ` Laurent Bercot [this message]
2015-03-23 11:45 ` Pablo Neira Ayuso
2015-03-23 13:32 ` nftables feature request: don't fail "flush" on nonexistent tables (was: nftables: nft fails to add rules to chains) Laurent Bercot
2015-03-23 19:42 ` Arturo Borrero Gonzalez
2015-03-24 10:06 ` nftables feature request: don't fail "flush" on nonexistent tables Laurent Bercot
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=550F1155.5000501@skarnet.org \
--to=ska-devel@skarnet.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.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