[Bug 1352] New: After adding map type ipv4_addr : counter it behaves as a set

[bugzilla-daemon at netfilter.org]

https://bugzilla.netfilter.org/show_bug.cgi?id=1352

            Bug ID: 1352
           Summary: After adding map type ipv4_addr : counter it behaves
                    as a set
           Product: nftables
           Version: unspecified
          Hardware: x86_64
                OS: Debian GNU/Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: nft
          Assignee: pablo at netfilter.org
          Reporter: arturo at debian.org

Original bug report: https://bugs.debian.org/931820


(using nftables 0.9.1 and linux 4.19)

after adding following map to nftables
# nft add map inet filter countermap { type ipv4_addr : counter\; }

the ruleset is, as expected

# nft list ruleset
table inet filter {
    map countermap {
        type ipv4_addr : counter
    }
}

but from now, you can't work with this as a map, but you have to use a
set. For example, when you run 

# nft flush map inet filter countermap
Error: No such file or directory
flush map inet filter countermap
                      ^^^^^^^^^^

you get an error, but it works with set keyword
# nft flush set inet filter countermap

It also doesn't appear in list of maps, but it's in list of sets...
# nft list maps
table inet filter {
}

# nft list sets
table inet filter {
    map countermap {
        type ipv4_addr : counter
    }
}

Everything about this set/map work as expected, you can use it in rules
and it works...

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20190711/42136c6f/attachment.html>