Bug 300841 - iptables placed AFTER network interface initialization
Summary: iptables placed AFTER network interface initialization
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iptables
Version: 7
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-21 17:23 UTC by Gabor Kovacs
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-09-25 09:47:52 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.