From: Florian Westphal <fw@strlen.de>
To: Stephen Satchell <list@satchell.net>
Cc: netfilter@vger.kernel.org
Subject: Re: Lint for nftables
Date: Mon, 3 Feb 2020 01:27:23 +0100 [thread overview]
Message-ID: <20200203002723.GP795@breakpoint.cc> (raw)
In-Reply-To: <e94e649a-0d30-6fd1-4144-4bb73564d0ff@satchell.net>
Stephen Satchell <list@satchell.net> wrote:
> Is there an equivalent to lint(1) for nftables? One that, instead of just
> saying "you blew it", it shows where you blew it and what it was expected.
No. nft is already supposed to tell you where the problem is.
Please provide an example error and we can try to improve the error
reporting.
next prev parent reply other threads:[~2020-02-03 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 19:23 Lint for nftables Stephen Satchell
2020-02-03 0:27 ` Florian Westphal [this message]
2020-02-03 13:14 ` Paweł Krawczyk
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=20200203002723.GP795@breakpoint.cc \
--to=fw@strlen.de \
--cc=list@satchell.net \
--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