Re: nft: parser problem, can use mark as datatype in sets and maps

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

On Mon, Aug 10, 2015 at 03:48:12PM +0200, Andreas Schultz wrote:
> Hi,
> 
> The data type definition for mark and the general idea of the parser
> indicate that the following nft statements should work:
>  
>   # nft add map filter MAP1 { type ipv4_addr : mark\; }
>   # nft add set filter SET1 { type mark\; }
> 
> However, both fail with a similar error message:
> 
>   <cmdline>:1:40-43: Error: syntax error, unexpected mark, expecting string
>   add map filter MAP1 { type ipv4_addr : mark; }
>   <cmdline>:1:28-31: Error: syntax error, unexpected mark, expecting string
>   add set filter SET1 { type mark; }
> 
> The problem is parser, it expects a string as data type spec, but
> mark is already declared as a token.
> 
> I don't have much experience with bison, so does anyone have a quick
> work-around for this?

This is fixed by 2baf59c ("parser_bison: allow to use mark as datatype
for maps and sets").