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.

Description of problem:
"in" is considered a keyword and thus prevented from being accepted as chain name. This behaviour changed since rhel-8.1.0.

Version-Release number of selected component (if applicable):
nftables-0.9.3-11.el8.x86_64
iptables-1.8.4-9.el8.x86_64

How reproducible:
always

Steps to Reproduce:
iptables -N in
nft list ruleset | tee rules.nft
nft flush ruleset
nft -f rules.nft

Actual results:
table ip filter {
	chain INPUT {
		type filter hook input priority filter; policy accept;
	}

	chain FORWARD {
		type filter hook forward priority filter; policy accept;
	}

	chain OUTPUT {
		type filter hook output priority filter; policy accept;
	}

	chain in {
	}
}
rules.nft:14:8-9: Error: syntax error, unexpected in, expecting string
	chain in {
	      ^^
rules.nft:16:1-1: Error: syntax error, unexpected '}'
}
^

Expected results:
successful rules load

Additional info:
double quotation marks cause another type of error:
Error: syntax error, unexpected quoted string, expecting string

Yes, this is due to upstream commit 57c2b152c5f08 ("src: add ipsec (xfrm)
expression") which added new keywords "in" and "out".

Basically it's the same issue as reported in bug 1658716, so marking this one
as a duplicate.

*** This bug has been marked as a duplicate of bug 1658716 ***