<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - docs/nft-wiki: verdict statements have incomplete documentation"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1699">1699</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>docs/nft-wiki: verdict statements have incomplete documentation
</td>
</tr>
<tr>
<th>Product</th>
<td>nftables
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P5
</td>
</tr>
<tr>
<th>Component</th>
<td>nft
</td>
</tr>
<tr>
<th>Assignee</th>
<td>pablo@netfilter.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>evil.function@proton.me
</td>
</tr></table>
<p>
<div>
<pre><a href="https://wiki.nftables.org/wiki-nftables/index.php/Quick_reference-nftables_in_10_minutes#Verdict_statements">https://wiki.nftables.org/wiki-nftables/index.php/Quick_reference-nftables_in_10_minutes#Verdict_statements</a>
Specifically the return statement, but the others could use some enhancement,
too.
As stated in the above wiki section, it sounds like a 'jump' /must/ have an
explicit 'return' in the jumped-to chain in order to return processing to the
calling chain. This is easily proven false by tsting:
chain base {
jump user_chain
counter # Will we get here? Yes, even though wiki implies otherwise.
}
chain user_chain {
counter
# Implicit, undocumented 'return' here...
}
Maybe something like this:
o return: Return from the current chain and continue at the next rule of the
last chain. In a base chain it is equivalent to accept. There is an implicit
'return' at the end of any user chain, such that a 'jump' to the chain will
return control to the statement following the 'jump' when none of the rules in
the user chain trigger a terminating verdict.
o jump <chain>: Continue at the first rule of <chain>. It will continue at the
next rule after a return statement is issued, or when processing reaches the
end of the chain.
o goto <chain>: Similar to jump, but after the new chain the evaluation will
continue at the last chain instead of the one containing the goto statement.
This is effectively a jump, but it never returns from the destination chain.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>