<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - nft generates wrong intervals for sets with auto-merge"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1438#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - nft generates wrong intervals for sets with auto-merge"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1438">bug 1438</a>
from <span class="vcard"><a class="email" href="mailto:kfm@plushkava.net" title="kfm@plushkava.net">kfm@plushkava.net</a>
</span></b>
<pre>I tested the given ruleset against nftables (commit c156232) and Linux 5.7.19,
including the net_set_rbtree patch mentioned in <a class="bz_bug_link
bz_status_NEW "
title="NEW - nft add element fails when preceded by nft get element or nft delete element commands"
href="show_bug.cgi?id=1451">bug 1451</a>. I changed "inet" to
"ip", just because it suits my existing ruleset. The following errors occur,
every time:
./test.nft:4:1-44: Error: Could not process rule: File exists
add element ip filter myset { 192.168.0.2 }
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
./test.nft:6:1-46: Error: Could not process rule: File exists
add element ip filter myset { 192.168.1.100 }
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I suppose that's an improvement on the behaviour that Timo is seeing, but
hardly ideal. It's clear that that there are are still issues concerning the
auto-merge functionality, as has also been stated in the 13th comment of <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - nft stalls on EAGAIN upon repeatedly flushing and populating a set"
href="show_bug.cgi?id=1392">bug
1392</a>.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>