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.

Bug 1571938

Summary: nftables: man page gives wrong keyword for "reject with icmp6"
Product: Red Hat Enterprise Linux 7 Reporter: Eric Garver <egarver>
Component: nftablesAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: Jiri Peska <jpeska>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.6CC: jpeska, todoleza
Target Milestone: rcKeywords: ManPageChange
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nftables-0.8-9.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:38:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Garver 2018-04-25 18:32:49 UTC
The keyword that nft actually accepts is "icmpv6".
e.g.

# nft add table inet firewalld
[root@dev-rhel7 firewalld]# nft add chain inet firewalld blah { type filter hook input priority 0 \; }
[root@dev-rhel7 firewalld]# nft add rule inet firewalld blah meta nfproto ipv6 reject with icmp6 type admin-prohibited
Error: syntax error, unexpected string, expecting icmp or icmpv6 or tcp or icmpx
add rule inet firewalld blah meta nfproto ipv6 reject with icmp6 type admin-prohibited
                                                           ^^^^^
[root@dev-rhel7 firewalld]# nft add rule inet firewalld blah meta nfproto ipv6 reject with icmpv6 type admin-prohibited



$ man nft
...
   REJECT STATEMENT
       reject [ with {icmp | icmp6 | icmpx} type {icmp_type | icmp6_type | icmpx_type} ]
       reject [ with {tcp} {reset} ]

Comment 2 Phil Sutter 2018-06-06 09:00:40 UTC
Fix submitted upstream: https://marc.info/?l=netfilter-devel&m=152827540006707&w=2

Comment 3 Phil Sutter 2018-06-06 10:57:16 UTC
Upstream accepted:

commit 9b3036bb9f00d6e244ed92e0e782c5617ae40b84 (origin/master, origin/HEAD)
Author: Phil Sutter <phil>
Date:   Wed Jun 6 10:56:26 2018 +0200

    nft.8: Fix reject statement documentation
    
    First of all, 'with icmp6' is invalid, expected is 'with icmpv6'. In
    addition to that, parameter 'type' expects an icmp*_code type, not
    icmp*_type. The respective table column was already correct, but in
    synopsis it was wrong.
    
    Signed-off-by: Phil Sutter <phil>
    Signed-off-by: Florian Westphal <fw>

Comment 8 errata-xmlrpc 2018-10-30 10:38:13 UTC
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-2018:3154