<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - add set - syntax has changed - update documentation"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1299#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - add set - syntax has changed - update documentation"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1299">bug 1299</a>
from <span class="vcard"><a class="email" href="mailto:fw@strlen.de" title="Florian Westphal <fw@strlen.de>"> <span class="fn">Florian Westphal</span></a>
</span></b>
<pre>(In reply to James Feeney from <a href="show_bug.cgi?id=1299#c2">comment #2</a>)
<span class="quote">> I'm confused. "filter" is just an arbitrary, but commonly used, table name,
> where the nft man page shows, in effect:
>
> add set <address_family> <arbitrary_table_name> <arbitrary_set_name> { ... }
>
> The table named "filter" can be seen to already exist from the result of
> "nft list tables".</span >
No.
table inet filter // inet family
table ip nat // ip family
table ip private // ip family
so, there is no table named "filter" in the ip family, only in the inet family.
$ nft add set filter foreign \{ type ipv4_addr \; \}
... tells nft to add a new set named foreign to a table named "filter" in the
ip family, but there is no such table.
'table ip filter' would make this work, albeit its probably not what was
intended. Using 'nft add set inet filter ..' tells nft do add a set to a table
named "filter" in the "inet" family, which does exist.
<span class="quote">> Or, do you mean to suggest that the table names are not arbitrary, and that
> nft has defined, but not documented, some limited set of allowed table names?</span >
No undocumented magic, they are just names/identifiers.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>