Bug 300841

Summary: iptables placed AFTER network interface initialization
Product: [Fedora] Fedora Reporter: Gabor Kovacs <kgabor>
Component: iptablesAssignee: Thomas Woerner <twoerner>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 7CC: sconklin
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-25 09:47:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gabor Kovacs 2007-09-21 17:23:11 UTC
Description of problem:
Iptables-1.3.8-2.fc7 is placed as an S26 (instead of S08) service by chkconfig
to /etc/rc.d/rcX.d/. This is definitely after bringing up network interfaces
which is undesirable. 

Steps to Reproduce:
1. Update to iptables-1.3.8-2.fc7
2. chkconfig --del iptables
3. chkconfig --add iptables
  
Actual results:
I get S26iptables in /etc/rc.d/rc3.d while having S10network.

Expected results:
SXXiptables number should be less than SXXnetwork.

Additional info:
In /etc/rc.d/init.d there is:
# Required-Start: $local_fs
local_fs is seemed to be provided by netfs, and this causes chkconfig to put
iptables after it in boot order.

Comment 1 Thomas Woerner 2007-09-25 09:47:52 UTC
Fixe din updates in package iptables-1.3.8-2.1 or newer.