Nftables: timeout > 24d20h31m23s becomes 49d17h2m47s

[Marco De Benedetto <debe@xxxxxxxxxxx>]

Hi all,

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 nftables compiled from git (2cb7425)
and Debian nftables 0.8.3-1~bpo9+1

--
thank you in advance,
Marco
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html