Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [linux PATCH v2 1/5] netfilter: nft_nat: include a flag attribute
Date: Tue, 1 Jul 2014 13:27:21 +0200	[thread overview]
Message-ID: <20140701112721.GB2951@localhost> (raw)
In-Reply-To: <20140701104553.6831.59253.stgit@nfdev.cica.es>

On Tue, Jul 01, 2014 at 12:46:01PM +0200, Arturo Borrero Gonzalez wrote:
> Both SNAT and DNAT (and the upcoming masquerade) can have additional
> configuration parameters, such as port randomization or NAT addressing
> persistence.
> We can cover these scenarios by simply adding a flag attribute for
> userspace to fill when needed.
> 
> The flags to use are defined in include/uapi/linux/netfilter/nf_nat.h,
>  NF_NAT_RANGE_MAP_IPS
>  NF_NAT_RANGE_PROTO_SPECIFIED
>  NF_NAT_RANGE_PROTO_RANDOM
>  NF_NAT_RANGE_PERSISTENT
>  NF_NAT_RANGE_PROTO_RANDOM_FULLY
>  NF_NAT_RANGE_PROTO_RANDOM_ALL
> 
> The caller must take care of not messing up with the flags, as they are
> added unconditionally to the final resulting nf_nat_range.
> 
> Signed-off-by: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
> ---
> v2: address Florian Westphal's comments: check all flag bits to be known.
> 
>  include/uapi/linux/netfilter/nf_nat.h    |    5 +++++
>  include/uapi/linux/netfilter/nf_tables.h |    2 ++
>  net/netfilter/nft_nat.c                  |   16 ++++++++++++++++
>  3 files changed, 23 insertions(+)
> 
> diff --git a/include/uapi/linux/netfilter/nf_nat.h b/include/uapi/linux/netfilter/nf_nat.h
> index 1ad3659..f42b118 100644
> --- a/include/uapi/linux/netfilter/nf_nat.h
> +++ b/include/uapi/linux/netfilter/nf_nat.h
> @@ -13,6 +13,11 @@
>  #define NF_NAT_RANGE_PROTO_RANDOM_ALL		\
>  	(NF_NAT_RANGE_PROTO_RANDOM | NF_NAT_RANGE_PROTO_RANDOM_FULLY)
>  
> +#define NF_NAT_RANGE_OPS_MASK			\
> +	(NF_NAT_RANGE_MAP_IPS|NF_NAT_RANGE_PROTO_SPECIFIED \
> +	 |NF_NAT_RANGE_PROTO_RANDOM|NF_NAT_RANGE_PERSISTENT \
> +	 |NF_NAT_RANGE_PROTO_RANDOM_FULLY)
> +
>  struct nf_nat_ipv4_range {
>  	unsigned int			flags;
>  	__be32				min_ip;
> diff --git a/include/uapi/linux/netfilter/nf_tables.h b/include/uapi/linux/netfilter/nf_tables.h
> index 2a88f64..92c211b 100644
> --- a/include/uapi/linux/netfilter/nf_tables.h
> +++ b/include/uapi/linux/netfilter/nf_tables.h
> @@ -773,6 +773,7 @@ enum nft_nat_types {
>   * @NFTA_NAT_REG_ADDR_MAX: source register of address range end (NLA_U32: nft_registers)
>   * @NFTA_NAT_REG_PROTO_MIN: source register of proto range start (NLA_U32: nft_registers)
>   * @NFTA_NAT_REG_PROTO_MAX: source register of proto range end (NLA_U32: nft_registers)
> + * @NFTA_NAT_FLAGS: additional NAT configuration (NF_NAT_RANGE_*) (NLA_U32)
>   */
>  enum nft_nat_attributes {
>  	NFTA_NAT_UNSPEC,
> @@ -782,6 +783,7 @@ enum nft_nat_attributes {
>  	NFTA_NAT_REG_ADDR_MAX,
>  	NFTA_NAT_REG_PROTO_MIN,
>  	NFTA_NAT_REG_PROTO_MAX,
> +	NFTA_NAT_FLAGS,
>  	__NFTA_NAT_MAX
>  };
>  #define NFTA_NAT_MAX		(__NFTA_NAT_MAX - 1)
> diff --git a/net/netfilter/nft_nat.c b/net/netfilter/nft_nat.c
> index 79ff58c..51bb05f 100644
> --- a/net/netfilter/nft_nat.c
> +++ b/net/netfilter/nft_nat.c
> @@ -33,6 +33,7 @@ struct nft_nat {
>  	enum nft_registers      sreg_proto_max:8;
>  	enum nf_nat_manip_type  type:8;
>  	u8			family;
> +	u32			flags;
>  };
>  
>  static void nft_nat_eval(const struct nft_expr *expr,
> @@ -71,6 +72,8 @@ static void nft_nat_eval(const struct nft_expr *expr,
>  		range.flags |= NF_NAT_RANGE_PROTO_SPECIFIED;
>  	}
>  
> +	range.flags |= priv->flags;
> +
>  	data[NFT_REG_VERDICT].verdict =
>  		nf_nat_setup_info(ct, &range, priv->type);
>  }
> @@ -82,6 +85,7 @@ static const struct nla_policy nft_nat_policy[NFTA_NAT_MAX + 1] = {
>  	[NFTA_NAT_REG_ADDR_MAX]	 = { .type = NLA_U32 },
>  	[NFTA_NAT_REG_PROTO_MIN] = { .type = NLA_U32 },
>  	[NFTA_NAT_REG_PROTO_MAX] = { .type = NLA_U32 },
> +	[NFTA_NAT_FLAGS]	 = { .type = NLA_U32 },
>  };
>  
>  static int nft_nat_init(const struct nft_ctx *ctx, const struct nft_expr *expr,
> @@ -149,6 +153,12 @@ static int nft_nat_init(const struct nft_ctx *ctx, const struct nft_expr *expr,
>  	} else
>  		priv->sreg_proto_max = priv->sreg_proto_min;
>  
> +	if (tb[NFTA_NAT_FLAGS]) {
> +		priv->flags = ntohl(nla_get_be32(tb[NFTA_NAT_FLAGS]));
> +		if (priv->flags &~ NF_NAT_RANGE_OPS_MASK)

Minor nitpick:

        if (priv->flags & ~NF_NAT_RANGE_MASK)

and I'd suggest a shorter name for the mask: NF_NAT_RANGE_MASK.


  reply	other threads:[~2014-07-01 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 10:45 [linux PATCH v2 0/5] NAT updates for nf_tables Arturo Borrero Gonzalez
2014-07-01 10:46 ` [linux PATCH v2 1/5] netfilter: nft_nat: include a flag attribute Arturo Borrero Gonzalez
2014-07-01 11:27   ` Pablo Neira Ayuso [this message]
2014-07-01 10:46 ` [linux PATCH v2 2/5] netfilter: nf_nat_masquerade_ipv4: code factorization Arturo Borrero Gonzalez
2014-07-01 10:46 ` [linux PATCH v2 3/5] netfilter: nf_nat_masquerade_ipv6: " Arturo Borrero Gonzalez
2014-07-01 10:47 ` [linux PATCH v2 4/5] netfilter: nft_nat: split code in AF parts Arturo Borrero Gonzalez
2014-07-01 11:25   ` Pablo Neira Ayuso
2014-07-01 10:47 ` [linux PATCH v2 5/5] netfilter: nft_nat: add masquerade support Arturo Borrero Gonzalez

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=20140701112721.GB2951@localhost \
    --to=pablo@netfilter.org \
    --cc=arturo.borrero.glez@gmail.com \
    --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