Bug 31136

Summary: iptables-restore fails on user-defined chains
Product: [Retired] Red Hat Raw Hide Reporter: Ben Liblit <liblit>
Component: iptablesAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0   
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: 2001-03-21 15:43:03 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 Ben Liblit 2001-03-09 02:11:51 UTC 
The iptables-restore program fails if the saved configuration uses any
user-defined chains as jump targets.  To show this in action, start off
with a clean system with no iptables rules defined.  Run the following
commands:

	# iptables -N user-chain
	# iptables -A INPUT -j user-chain
	# service iptables save
	# service iptables restart

After thre restart command you will see the following diagnostic output:

	iptables-restore v1.2: Couldn't load target
`user-chain':/lib/iptables/libipt_user-chain.so:
	cannot open shared object file: No such file or directory

	Try `iptables-restore -h' or 'iptables-restore --help' for more
information.

An "iptables -L" command confirms that the tables have not been restored. 
Direct inspection of the saved "/etc/sysconfig/iptables" file reveals no
problems in the file itself, suggesting that the bug is on the
iptables-restore side rather than the iptables-save side.

I observe this bug in the "iptables-1.2.0-10" RPM.
Comment 1 Gerald Teschl 2001-03-21 09:33:49 UTC 

*** This bug has been marked as a duplicate of 28412 ***
Comment 2 David Lawrence 2001-03-21 15:42:21 UTC 
Reopening bug since it was marked as a duplicate of a private bug which has not
been resolved yet. Bero, please add a comment to this bug on what the fix is
when the private bug is resolved.
Comment 3 Bernhard Rosenkraenzer 2001-03-21 20:29:13 UTC 
Fixed in 1.2.1a-1