Bug 74518

Summary: iptables modules load even if no firewall used
Product: [Retired] Red Hat Linux Reporter: David Morse <david_j_morse>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: low    
Version: 8.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-14 05:26:08 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 David Morse 2002-09-25 19:33:40 UTC
Description of Problem:

Due to the way ifup checks for firewall existence, it actually loads iptables 
modules and they stay resident after bootup, even if the user chose no firewall 
at install time:

# Is there a firewall running, and does it look like one we configured?
FWACTIVE=
if iptables -L -n 2>/dev/null | grep -q RH-Lokkit-0-50-INPUT ; then
    FWACTIVE=1
fi

the iptables command above is what triggers the iptable_filter and ip_tables 
modules to load:

[root@papp100 root]# lsmod
Module                  Size  Used by    Not tainted
[..]
iptable_filter          2412   0  (autoclean) (unused)
ip_tables              14936   1  [iptable_filter]
[..]

Version-Release number of selected component (if applicable): 6.95-1


How Reproducible:  Every time.


Steps to Reproduce:
1. Boot the system
2. /sbin/lsmod

Actual Results:  ip_tables and iptable_filter modules load even if user has no 
firewall

Expected Results:  Modules above shouldn't be loaded if there are no firewall 
rules


Additional Information:
	
This could be confusing to users who chose "no firewall" yet see iptables 
modules loaded when doing an lsmod.

Comment 1 Bill Nottingham 2003-01-14 05:26:08 UTC
Changed in 7.03-1.