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 1853774 - iptables-services load sysctl.d/ indiscriminately of .conf suffix
Summary: iptables-services load sysctl.d/ indiscriminately of .conf suffix
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iptables
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Phil Sutter
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-03 22:24 UTC by Tomas Dolezal
Modified: 2020-11-04 01:55 UTC (History)
2 users (show)

Fixed In Version: iptables-1.8.4-15.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:54:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4518 0 None None None 2020-11-04 01:55:11 UTC

Description Tomas Dolezal 2020-07-03 22:24:28 UTC
Description of problem:
On rhel8 the sysctl.d is governed by systemd (man:SYSCTL.D(5)) which describes that only applicable files in allowed paths are of '*.conf' format. iptables initscript does not reflect that in its load_sysctl function that seeks in '/etc/sysctl.d/*' glob.

Version-Release number of selected component (if applicable):
iptables-1.8.4-10.el8_2.1.x86_64

How reproducible:
always

Steps to Reproduce:
uncomment following line in /etc/sysconfig/iptables-config:
#IPTABLES_SYSCTL_LOAD_LIST=".nf_conntrack .bridge-nf
use e.g.
echo 'net.nf_conntrack_max = 120838' >> /etc/sysctl.d/foo.anysuffix
restart iptables service

Actual results:
sysctl from any file is loaded

Expected results:
.conf suffixes are respected

Additional info:

Comment 2 Phil Sutter 2020-07-06 16:05:50 UTC
This should be a trivial RHEL-only fix to iptables init script like so:

--- a/iptables.init
+++ b/iptables.init
@@ -134,7 +134,7 @@ load_sysctl() {
         echo -n $"Loading sysctl settings: "
         ret=0
         for item in $IPTABLES_SYSCTL_LOAD_LIST; do
-            fgrep -hs $item /etc/sysctl.d/* | sysctl -p - >/dev/null
+            fgrep -hs $item /etc/sysctl.d/*.conf | sysctl -p - >/dev/null
             let ret+=$?;
         done
         [ $ret -eq 0 ] && success || failure

Comment 8 errata-xmlrpc 2020-11-04 01:54:58 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 (iptables bug fix and enhancement update), 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-2020:4518


Note You need to log in before you can comment on or make changes to this bug.