netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 3/4] evaluate: no check the network context in reject with tcp reset reason
Date: Tue, 21 Oct 2014 09:55:45 +0200	[thread overview]
Message-ID: <20141021075544.GA3220@salvia> (raw)
In-Reply-To: <1413847780-10149-3-git-send-email-alvaroneay@gmail.com>

On Tue, Oct 21, 2014 at 01:29:39AM +0200, Alvaro Neira Ayuso wrote:
> nft add rule -nnn bridge test-bridge input \
> 			ip protocol tcp reject with tcp reset
> 
> If we use in reject the type tcp reset. We don't need to check if the network
> context is compatible with the reason. This patch fix that.
> 
> Signed-off-by: Alvaro Neira Ayuso <alvaroneay@gmail.com>
> ---
>  src/evaluate.c |   80 +++++++++++++++++++++++++++++++++-----------------------
>  1 file changed, 47 insertions(+), 33 deletions(-)
> 
> diff --git a/src/evaluate.c b/src/evaluate.c
> index 20235a8..8b19baf 100644
> --- a/src/evaluate.c
> +++ b/src/evaluate.c
> @@ -1208,24 +1208,31 @@ static int stmt_evaluate_reject_inet(struct eval_ctx *ctx, struct stmt *stmt,
>  	const struct proto_desc *desc, *base;
>  	int protocol;
>  
> -	base = ctx->pctx.protocol[PROTO_BASE_LL_HDR].desc;
> -	desc = ctx->pctx.protocol[PROTO_BASE_NETWORK_HDR].desc;
> -	if (desc != NULL) {
> -		protocol = proto_find_num(base, desc);
> -		switch (protocol) {
> -		case NFPROTO_IPV4:
> -			if (stmt->reject.family == NFPROTO_IPV4)
> -				return 0;
> -			return stmt_error(ctx, stmt,
> -			  "conflicting protocols specified: ip vs ip6");
> -		case NFPROTO_IPV6:
> -			if (stmt->reject.family == NFPROTO_IPV6)
> -				return 0;
> -			return stmt_error(ctx, stmt,
> -			  "conflicting protocols specified: ip vs ip6");
> -		default:
> -			BUG("unsupported family");
> +	switch (stmt->reject.type) {
> +	case NFT_REJECT_TCP_RST:
> +		break;
> +	case NFT_REJECT_ICMPX_UNREACH:

Do you really need to check layer 3 conflicts with icmpx?

> +	case NFT_REJECT_ICMP_UNREACH:
> +		base = ctx->pctx.protocol[PROTO_BASE_LL_HDR].desc;
> +		desc = ctx->pctx.protocol[PROTO_BASE_NETWORK_HDR].desc;
> +		if (desc != NULL) {
> +			protocol = proto_find_num(base, desc);
> +			switch (protocol) {
> +			case NFPROTO_IPV4:
> +				if (stmt->reject.family == NFPROTO_IPV4)
> +					return 0;
> +				return stmt_error(ctx, stmt,
> +				  "conflicting protocols specified: ip vs ip6");
> +			case NFPROTO_IPV6:
> +				if (stmt->reject.family == NFPROTO_IPV6)
> +					return 0;
> +				return stmt_error(ctx, stmt,
> +				  "conflicting protocols specified: ip vs ip6");
> +			default:
> +				BUG("unsupported family");
> +			}
>  		}
> +		break;
>  	}
>  	if (stmt->reject.type == NFT_REJECT_ICMPX_UNREACH)
>  		return 0;

  reply	other threads:[~2014-10-21  7:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 23:29 [nft PATCH 1/4] evaluate: refactor function to check the reject family in inet and bridge Alvaro Neira Ayuso
2014-10-20 23:29 ` [nft PATCH 2/4] evaluate: accept a reject reason with incorrect network context Alvaro Neira Ayuso
2014-10-20 23:29 ` [nft PATCH 3/4] evaluate: no check the network context in reject with tcp reset reason Alvaro Neira Ayuso
2014-10-21  7:55   ` Pablo Neira Ayuso [this message]
2014-10-21 12:32     ` Álvaro Neira Ayuso
2014-10-20 23:29 ` [nft PATCH 4/4 v3] evaluate: fix a crash if we check the transport protocol is tcp Alvaro Neira Ayuso
2014-10-21  8:15   ` Pablo Neira Ayuso
2014-10-21 12:28     ` Álvaro Neira Ayuso
2014-10-21  8:45 ` [nft PATCH 1/4] evaluate: refactor function to check the reject family in inet and bridge 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=20141021075544.GA3220@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).