From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alvaro Neira Ayuso <alvaroneay@gmail.com>
Cc: netfilter-devel@vger.kernel.org, kaber@trash.net
Subject: Re: [nft PATCH 2/2 v2] evaluate: reject: enhance the error support throwing message with more details
Date: Fri, 24 Oct 2014 12:04:27 +0200 [thread overview]
Message-ID: <20141024100427.GB4806@salvia> (raw)
In-Reply-To: <1414085817-9059-2-git-send-email-alvaroneay@gmail.com>
On Thu, Oct 23, 2014 at 07:36:57PM +0200, Alvaro Neira Ayuso wrote:
> If we add a rule like:
>
> nft add rule bridge filter input ether type ip reject with icmpv6 type no-route
>
> We throw an error like:
>
> <cmdline>:1:44-49: Error: conflicting protocols specified: ip vs ip6
> add rule bridge filter input ether type ip reject with icmpv6 type no-route
>
> Now, we are going to show in which part of the rule, we have the conflict:
>
> <cmdline>:1:51-75: Error: conflicting protocols specified: ip vs ip6
> add rule bridge filter input ether type ip reject with icmpv6 type no-route
> ~~~~~~~~~~~~~ ^^^^^^^^^^^^^^^^^^^^^^^^^
Applied, thanks.
next prev parent reply other threads:[~2014-10-24 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 17:36 [nft PATCH 1/2 v2] evaluate: reject: check the context in reject without reason for bridge and inet tables Alvaro Neira Ayuso
2014-10-23 17:36 ` [nft PATCH 2/2 v2] evaluate: reject: enhance the error support throwing message with more details Alvaro Neira Ayuso
2014-10-24 10:04 ` Pablo Neira Ayuso [this message]
2014-10-24 10:04 ` [nft PATCH 1/2 v2] evaluate: reject: check the context in reject without reason for bridge and inet tables Pablo Neira Ayuso
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=20141024100427.GB4806@salvia \
--to=pablo@netfilter.org \
--cc=alvaroneay@gmail.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.