<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - "nft -s list ruleset" should include "flush ruleset" as first line"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1696#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - "nft -s list ruleset" should include "flush ruleset" as first line"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1696">bug 1696</a>
from <span class="vcard"><a class="email" href="mailto:apachez@gmail.com" title="Apachez <apachez@gmail.com>"> <span class="fn">Apachez</span></a>
</span></b>
<pre>(In reply to Phil Sutter from <a href="show_bug.cgi?id=1696#c5">comment #5</a>)
<span class="quote">> (In reply to Apachez from <a href="show_bug.cgi?id=1696#c2">comment #2</a>)
> > Because when taking a backup I would expect it to be able to restore without
> > having to reboot the full box, and also be able to restore without throwing
> > out all sort of hard to troubleshoot errors such as:
> >
> > # BUG: invalid input descriptor type 1634164560
> > # nft: erec.c:161: erec_print: Assertion `0' failed.
>
> That's a bug, but you will see "funny" things like duplicate rules.
> Basically,
> doing 'nft list ruleset | nft -f -' is doing a non-flushing restore. Ignoring
> this detail while implementing or simulating a system service is a problem
> software shouldn't solve IMHO.</span >
Hence why a "save" and "restore" option should exist in the nft binary.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>