Re: [PATCH v2] extensions: libxt_limit: Add translation to nft

[Pablo Neira Ayuso <pablo@netfilter.org>]

On Wed, Dec 23, 2015 at 03:25:21AM +0530, Shivani Bhardwaj wrote:
> Add translation for module limit to nftables.
> 
> Examples:
> 
> $ sudo iptables-translate -A INPUT -m limit --limit 5/s
> nft add rule ip filter INPUT limit rate 5/second counter
> 
> $ sudo iptables-translate -A INPUT -m limit --limit 3/m --limit-burst 3
> nft add rule ip filter INPUT limit rate 3/minute burst 3 packets counter

Applied with minor glitch.

> diff --git a/extensions/libxt_limit.c b/extensions/libxt_limit.c
> index f75ef2f..1874686 100644
> --- a/extensions/libxt_limit.c
> +++ b/extensions/libxt_limit.c
> @@ -25,8 +25,8 @@ static void limit_help(void)
>  {
>  	printf(
>  "limit match options:\n"
> -"--limit avg			max average match rate: default "XT_LIMIT_AVG"\n"
> -"                                [Packets per second unless followed by \n"
> +"--limit avg		max average match rate: default "XT_LIMIT_AVG"\n"
> +"                                [Packets per second unless followed by\n"
>  "                                /sec /minute /hour /day postfixes]\n"
>  "--limit-burst number		number to match in a burst, default %u\n",
>  XT_LIMIT_BURST);
> @@ -73,7 +73,8 @@ int parse_rate(const char *rate, uint32_t *val)
>  		 * The rate maps to infinity. (1/day is the minimum they can
>  		 * specify, so we are ok at that end).
>  		 */
> -		xtables_error(PARAMETER_PROBLEM, "Rate too fast \"%s\"\n", rate);
> +		xtables_error(PARAMETER_PROBLEM,
> +			      "Rate too fast \"%s\"\n", rate);
>  	return 1;
>  }
>  
> @@ -86,10 +87,11 @@ static void limit_init(struct xt_entry_match *m)
>  
>  }
>  
> -/* FIXME: handle overflow:
> -	if (r->avg*r->burst/r->burst != r->avg)
> -		xtables_error(PARAMETER_PROBLEM,
> -			   "Sorry: burst too large for that avg rate.\n");
> +/*
> + * FIXME: handle overflow:
> + * if (r->avg*r->burst/r->burst != r->avg)
> + *	xtables_error(PARAMETER_PROBLEM,
> + *	"Sorry: burst too large for that avg rate.\n");
>  */
>  
>  static void limit_parse(struct xt_option_call *cb)
> @@ -128,8 +130,8 @@ static void print_rate(uint32_t period)
>  	}
>  
>  	for (i = 1; i < ARRAY_SIZE(rates); ++i)
> -		if (period > rates[i].mult
> -            || rates[i].mult/period < rates[i].mult%period)
> +		if (period > rates[i].mult ||
> +		    rates[i].mult / period < rates[i].mult % period)
>  			break;
>  
>  	printf(" %u/%s", rates[i-1].mult / period, rates[i-1].name);
> @@ -139,6 +141,7 @@ static void
>  limit_print(const void *ip, const struct xt_entry_match *match, int numeric)
>  {
>  	const struct xt_rateinfo *r = (const void *)match->data;
> +
>  	printf(" limit: avg"); print_rate(r->avg);
>  	printf(" burst %u", r->burst);
>  }

These cleanup above, you better place them next time in a separated
initial patch. I have keep them back.

> @@ -152,6 +155,43 @@ static void limit_save(const void *ip, const struct xt_entry_match *match)
>  		printf(" --limit-burst %u", r->burst);
>  }
>  
> +static const struct rates rates_xlate[] = {
> +		{ "day", XT_LIMIT_SCALE*24*60*60 },
> +		{ "hour", XT_LIMIT_SCALE*60*60 },
> +		{ "minute", XT_LIMIT_SCALE*60 },
> +		{ "second", XT_LIMIT_SCALE } };

I have reorganized this array definition, see what I applied so you
follow the same pattern next time.

Thanks.