Skip to contentSkip to conversation

Implicit flow tables can't be listed

DISCUSSION Florian Westphal 2 participants 4 messages Jun 16, 2016 – Jun 23, 2016 netfilter

lore
Share & tools
lore

Florian Westphal

author maintainer
#0 lore raw

nft currently can't list implicit flow tables, e.g.:

nft add rule ip filter forward flow { ip daddr counter }

... will work, and it shows up in

'nft list flow tables' as 'flow table __ft0' (or some other number) but

nft list flow table filter __ft0
... will error out ('unexpected junk, expecting string').

We can either teach scanner.l that __ft{decstring} is a string, or force users to always provide a name.

Any preference?

Thanks.

#1 lore raw

Hi Florian,

Quoted 8 lines · Florian Westphal

nft currently can't list implicit flow tables, e.g.:

nft add rule ip filter forward flow { ip daddr counter }

... will work, and it shows up in

'nft list flow tables' as 'flow table __ft0' (or some other number) but

Quoted 7 lines

nft list flow table filter __ft0
... will error out ('unexpected junk, expecting string').

We can either teach scanner.l that __ft{decstring} is a string, or force users to always provide a name.

Any preference?

How can we actually relate the rule with the flow table if we have several anonymous flow tables?

More thoughts on flow tables thing. I think we should explore flow table declarations support like:

table ip filter {
        flow table ft {
                ip saddr counter
                # content here
        }

        chain forward {
                type filter hook forward priority 0;
                flow @ft
        }

So we can dereference existing flow tables from rules.

This also provides a way to restore blacklist/whitelist in case we want to save them into file and restore them later. The original idea is that flow tables contain volatile information, but I think someone may want to store the current state into file and restore it, eg. in case it needs to reboot the system.

Moreover, the output of the list flow tables command in nft should be parseable, as it is the case for the existing object listings.

This needs a bit of code update so we can get the listing working properly (currently what Pablo Bermudo added is a bit of a hack just to allow people inspect their content, but as I said in the nft 0.6 announcement, this output format is not stable).

author maintainer
#2 lore raw
Quoted 2 lines · Pablo Neira Ayuso

How can we actually relate the rule with the flow table if we have several anonymous flow tables?

nft list table filter

table ip filter {
        chain input {
                type filter hook input priority 0; policy accept;
                flow table __ft0 { ip saddr counter packets 0 bytes 0}
                flow table __ft1 { ip daddr counter packets 0 bytes 0}
        }

... so the internal name will be shown.

[..]

Quoted 5 lines

This also provides a way to restore blacklist/whitelist in case we want to save them into file and restore them later. The original idea is that flow tables contain volatile information, but I think someone may want to store the current state into file and restore it, eg. in case it needs to reboot the system.

Agree.

#3 lore raw
Quoted 5 lines · Florian Westphal
Quoted 2 lines · Pablo Neira Ayuso

How can we actually relate the rule with the flow table if we have several anonymous flow tables?

nft list table filter

Quoted 8 lines
table ip filter {
        chain input {
                type filter hook input priority 0; policy accept;
                flow table __ft0 { ip saddr counter packets 0 bytes 0}
                flow table __ft1 { ip daddr counter packets 0 bytes 0}
        }

... so the internal name will be shown.

OK, then enhance the scanner to catch __ and run tests to validate. I don't think this break anything.