Re: [nft PATCH 8/9] JSON: Make match op mandatory, introduce 'in' operator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 29, 2018 at 04:23:27PM +0200, Phil Sutter wrote:
> diff --git a/doc/libnftables-json.adoc b/doc/libnftables-json.adoc
> index 309988bcf02af..c174a35487d46 100644
> --- a/doc/libnftables-json.adoc
> +++ b/doc/libnftables-json.adoc
> @@ -577,8 +577,6 @@ processing continues with the next rule in the same chain.
>  	Operator indicating the type of comparison.
>  
>  ==== OPERATORS
> -The operator is usually optional and if omitted usually defaults to "==".
> -Allowed operators are:
>  
>  [horizontal]
>  *&*:: Binary AND
> @@ -592,6 +590,17 @@ Allowed operators are:
>  *>*:: Greater than
>  *<=*:: Less than or equal to
>  *>=*:: Greater than or equal to
> +*in*:: Perform a lookup, i.e. test if bits on RHS are contained in LHS value

Applied, but only one comment on this one, 'in' maps to the internal
implicit operation? I'm a bit confused about this one.

Thanks!



[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux