[Bug 1299] add set - syntax has changed - update documentation

[bugzilla-daemon at netfilter.org]

https://bugzilla.netfilter.org/show_bug.cgi?id=1299

--- Comment #6 from James Feeney <james at nurealm.net> ---
>From the man page: "All nftables objects exist in address family specific
namespaces, therefore all identifiers include an address family."

I'm thinking that a few obvious-in-retrospect examples of "address family
specific namespace objects" would be very helpful, at this point in the man
page, to emphasize the significance of this point.

In particular, again in retrospect, the man page says quite plainly "nftables
objects".  Now, apparently, "nftables objects" is referring to "table", and
then, "identifiers" is referring to "table name".  But that is not
"spelled-out" explicitly, and it should be made explicit.

"All nftables objects exist in address family specific namespaces, therefore
all identifiers include an address family. If an identifier is specified
without an  address family, the ip family is used by default."

The two sentences in that paragraph are so abstract and succinct that they seem
almost "throwaway".  Instead, they are very very important to understand and
appreciate.

Yeah, I'm being a bit lame here, simply "RTFM", but maybe I'm not the only one.
 A bold subsection header would also be appropriate there, maybe "TABLES AND
TABLE NAMES" or some such.

And then also, include the bit about that the "inet" address family is *not*
simply "the sum" of the "ip" address family and the "ip6" address family, which
is what seems to be otherwise implied by the descriptions, in context:

  ip     IPv4 address family.
  ip6    IPv6 address family.
  inet   Internet (IPv4/IPv6) address family.

In other words, the "inet" address family requires some different sort of
definition/description.  "IPv4/IPv6 address family" is misleading.

-- 
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20181117/d262bd50/attachment.html>