[Bug 1237] New: sets: timeout > 24d20h31m23s becomes 49d17h2m47s

[bugzilla-daemon at netfilter.org]

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

            Bug ID: 1237
           Summary: sets: timeout > 24d20h31m23s becomes 49d17h2m47s
           Product: nftables
           Version: unspecified
          Hardware: x86_64
                OS: Debian GNU/Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: nft
          Assignee: pablo at netfilter.org
          Reporter: debe at galliera.it

I would like to use a timeout of 30 days for elements in a set but it
seems there is a some kind of problem above 24d20h31m23s.

# nft add table foo
# nft add set foo bar { type ether_addr\; timeout 24d20h31m23s \; }
# nft list set foo bar
table ip foo {
        set bar {
                type ether_addr
                timeout 24d20h31m23s
        }
}
# nft delete set foo bar
# nft add set foo bar { type ether_addr\; timeout 24d20h31m24s \; }
# nft list set foo bar
table ip foo {
        set bar {
                type ether_addr
                timeout 49d17h2m47s
        }
}

It seems that every timeout > 24d20h31m23s is interpreted as 49d17h2m47s.

I am experiencing this with both:
 1. nftables compiled from git 2cb7425 and libnftnl d58ea1f
 2. and Debian nftables 0.8.3-1~bpo9+1, libnftnl7 1.0.9-2~bpo9+1

-- 
thank you,
Marco

-- 
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/20180325/b58824e4/attachment.html>