From: Pablo Neira Ayuso <pablo@netfilter.org>
To: giorgio.nicole@arcor.de
Cc: netfilter@vger.kernel.org
Subject: Re: Re: nft 'script' not working
Date: Tue, 20 Oct 2015 15:42:48 +0200 [thread overview]
Message-ID: <20151020134121.GA916@salvia> (raw)
In-Reply-To: <512001352.171753.1445344666801.JavaMail.ngmail@webmail12.arcor-online.net>
On Tue, Oct 20, 2015 at 02:37:46PM +0200, giorgio.nicole@arcor.de wrote:
> Hi,
>
> thanks for your answer,
>
> your answer to the first question confirms what I already supposed,
> my workaround is now to add a last 'drop' rule to the input table
> instead of changing the table policy:
>
> add rule inet filter input drop
>
> instead of
>
> add chain inet filter input { policy drop; }
You also can specify the policy by the time you create the basechain
in one go:
add table inet filter
add chain inet filter input { type filter hook input priority 0; policy drop; }
prev parent reply other threads:[~2015-10-20 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 8:02 nft 'script' not working giorgio.nicole
2015-10-20 10:39 ` Pablo Neira Ayuso
2015-10-20 12:37 ` Aw: " giorgio.nicole
2015-10-20 13:42 ` Pablo Neira Ayuso [this message]
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=20151020134121.GA916@salvia \
--to=pablo@netfilter.org \
--cc=giorgio.nicole@arcor.de \
--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