Signed-off-by: Christoph Anton Mitterer --- doc/data-types.txt | 1 + doc/nft.txt | 10 ++++++++++ 2 files changed, 11 insertions(+) diff --git a/doc/data-types.txt b/doc/data-types.txt index 47a0d25a..dad7e31b 100644 --- a/doc/data-types.txt +++ b/doc/data-types.txt @@ -40,6 +40,7 @@ For example `tcp flags syn,ack / syn,ack,fin,rst` is the same as It should further be noted that *'expression' 'bit'[,'bit']...* is not the same as *'expression' {'bit'[,'bit']...}*. +See <> above. STRING TYPE diff --git a/doc/nft.txt b/doc/nft.txt index 3fef1882..4d1daf5c 100644 --- a/doc/nft.txt +++ b/doc/nft.txt @@ -764,6 +764,16 @@ Example: When the set contains range *1.2.3.1-1.2.3.4*, then adding element *1.2 effect. Adding *1.2.3.5* changes the existing range to cover *1.2.3.1-1.2.3.5*. Without this flag, *1.2.3.2* can not be added and *1.2.3.5* is inserted as a new entry. +Equality of a value with a set is given if the value matches exactly one value +in the set. +It shall be noted that for bitmask values this means, that +*'expression' 'bit'[,'bit']...* (which yields true if *any* of the bits are set) +is not the same as *'expression' {'bit'[,'bit']...}* (which yields true if +exactly one of the bits are set). +It may however be (effectively) the same, in cases like +`ct state established,related` and `ct state {established,related}`, where these +states are mutually exclusive. + MAPS ----- [verse] -- 2.51.0