Bug 51078

Summary: .../ini.d/iptables cannot parse spaces in log-prefixes in /etc/sysconfig/iptables
Product: [Retired] Red Hat Linux Reporter: Andrew Nelson <andrew>
Component: iptablesAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: tommy.mcneely
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-08-25 09:38:37 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:
Attachments:
Description Flags
Sequence of commands to generate and work-around problem
none
Sequence of commands to generate and work-around problem none

Description Andrew Nelson 2001-08-07 04:17:14 UTC
Description of Problem:
When using the init script, iptables, to load rules 
from /etc/sysconfig/iptables (that was created by 
using .../init.d/iptables save) an the load fails if a log-
prefix "{prefix}" has any spaces

How Reproducible:
Manually create rule with log-prefix using space(s); save rules with 
`iptables save`; load rules with iptables start

I have attached a file demonstrating the sequence of events.

Additional Information:
RH7.1, kernel 2.4.3-12

Comment 1 Andrew Nelson 2001-08-07 04:18:49 UTC
Created attachment 26554 [details]
Sequence of commands to generate and work-around problem

Comment 2 Andrew Nelson 2001-08-07 04:21:06 UTC
Created attachment 26555 [details]
Sequence of commands to generate and work-around problem

Comment 3 Bernhard Rosenkraenzer 2001-08-25 09:38:33 UTC
*** Bug 52550 has been marked as a duplicate of this bug. ***

Comment 4 Bernhard Rosenkraenzer 2001-08-25 09:39:25 UTC
This is fixed in 1.2.2-3


Comment 5 Tommy McNeely 2001-08-27 23:48:14 UTC
Should we use the Roswell2 beta package? or will this break things? 

Where should this update appear.. I cannot seem to get it from up2date.

Tommy