From: Florian Westphal <fw@strlen.de>
To: "Lars Noodén" <lars.nooden@gmx.com>
Cc: Linux Netfilter Users List <netfilter@vger.kernel.org>
Subject: Re: Found extra tables in nft ruleset
Date: Fri, 6 Mar 2020 14:08:00 +0100 [thread overview]
Message-ID: <20200306130800.GN979@breakpoint.cc> (raw)
In-Reply-To: <bd9702b2-0c75-96ba-24b8-b8ad05c50813@gmx.com>
Lars Noodén <lars.nooden@gmx.com> wrote:
> It's looking like nft is creating some extra tables when I create a chain.
>
> Seen below, I can clear the ruleset and then create a table and only the
> table I created is in the otherwise empty ruleset. However, if I add a
> chain to that table, then two unasked for tables get created, but
> perhaps not used. I'm not sure if they are supposed to be there or if
> they should be used.
THey are not supposed to be there.
> Is this an error on my part? If so what?
Run 'nft monitor' to figure out what adds them.
next prev parent reply other threads:[~2020-03-06 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 12:52 Found extra tables in nft ruleset Lars Noodén
2020-03-06 13:08 ` Florian Westphal [this message]
2020-03-06 13:22 ` Lars Noodén
2020-03-09 16:31 ` Lars Noodén
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=20200306130800.GN979@breakpoint.cc \
--to=fw@strlen.de \
--cc=lars.nooden@gmx.com \
--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