Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Laurent Bercot <ska-devel@skarnet.org>
To: netfilter@vger.kernel.org
Subject: nftables: nft fails to add rules to chains
Date: Thu, 19 Mar 2015 21:24:09 +0100	[thread overview]
Message-ID: <550B3069.7080209@skarnet.org> (raw)


  Hello,

  (Platform: Intel Atom (x86_64), Linux 3.19.1, musl 1.1.7,
latest nftables/libnftnl/libmnl from git. All iptables modules
out of the kernel, all necessary nftables modules in.)

  I can flush tables, create tables and create chains with nft
without trouble; however, every time I try and add a rule to
a chain, no matter what chain, no matter in what table, I get
the following error:

  netlink.c:182: Memory allocation failure

  I dug a bit and found that the error always happens when
alloc_nft_expr() is called for the *first* time (which is also
the last, since nft exits at that point...) and it is always
called with the argument "payload".

  What is happening ? Anything I could do to help fix it ?
  Thanks,

-- 
  Laurent


             reply	other threads:[~2015-03-19 20:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 20:24 Laurent Bercot [this message]
2015-03-21 20:16 ` nftables: nft fails to add rules to chains 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
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=550B3069.7080209@skarnet.org \
    --to=ska-devel@skarnet.org \
    --cc=netfilter@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