Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDavide F Bragalone
2018-09-14 14:33:21 UTC
Description of problem:
vmap is not documented in nft man page, there are just it is only in some examples).
Version-Release number of selected component (if applicable):
nftables-0.8-7.el7
Not sure if adding info in man pages is the best solution here. If not, I can ask the doc-team to elaborate more about nft usage in the next RHEL8 networking documentation.
Thanks,
Davide
Hi Davide,
(In reply to Davide F Bragalone from comment #0)
> Description of problem:
> vmap is not documented in nft man page, there are just it is only in some
> examples).
>
>
> Version-Release number of selected component (if applicable):
> nftables-0.8-7.el7
>
>
> Not sure if adding info in man pages is the best solution here. If not, I
> can ask the doc-team to elaborate more about nft usage in the next RHEL8
> networking documentation.
Yes, lack of vmap statement is a deficit in nft man page and I think it is the best spot to document it.
Meanwhile you may point the customer at https://wiki.nftables.org/wiki-nftables/index.php/Dictionaries (wiki.nftables.org is a good resource in general).
Cheers, Phil
Upstream commit to backport:
commit 3b29acc8f29944c5cf34259f2e2b5b40b4d0ccdd (origin/master, origin/HEAD)
Author: Phil Sutter <phil>
Date: Tue Apr 2 15:36:42 2019 +0200
doc: Add minimal description of (v)map statements
Although quite useful, these were missing in man page. Content loosely
based on wiki documentation.
Signed-off-by: Phil Sutter <phil>
Signed-off-by: Pablo Neira Ayuso <pablo>
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:2215