Alexander Mikhalitsyn <alexander.mikhalitsyn@xxxxxxxxxxxxx> wrote: > Currently, state_xlate_print function prints statemask > without { ... } around. But if ctstate condition is > negative, then we have to use { ... } after "!=" operator > > Reproducer: > $ iptables -A INPUT -d 127.0.0.1/32 -p tcp -m conntrack ! --ctstate RELATED,ESTABLISHED -j DROP > $ nft list ruleset > ... > meta l4proto tcp ip daddr 127.0.0.1 ct state != related,established counter packets 0 bytes 0 drop > ... > > it will fail if we try to load this rule: > $ nft -f nft_test > ../nft_test:6:97-97: Error: syntax error, unexpected comma, expecting newline or semicolon I'd suggest to use the 'foo & 1' notation just like for patch 2, it avoids the set lookup.