Bug 631290 - SuSEfirewall2 complains while boot
Summary: SuSEfirewall2 complains while boot
Status: RESOLVED DUPLICATE of bug 340926
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: i586 openSUSE 11.3
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Ludwig Nussel
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-14 20:53 UTC by Lars Müller
Modified: 2013-01-15 11:48 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: No
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Müller 2010-08-14 20:53:38 UTC
From /var/log/boot.msg:

<notice -- Aug 14 22:21:30.948071000> service cron done<notice -- Aug 14 22:21:30.956088000> service SuSEfirewall2_setup startStarting Firewall Initialization (phase 2 of 2) SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext'
SuSEfirewall2: Error: target must be a single host in FW_FORWARD_MASQ -> ##
SuSEfirewall2: Error: target must be a single host in FW_FORWARD_MASQ -> Type:
SuSEfirewall2: Error: target must be a single host in FW_FORWARD_MASQ -> string

In /etc/sysconfig/SuSEfirewall2 I found after the upgrade from openSUSE 11.2 via zypper up zypper; zypper dup:

FW_FORWARD_MASQ="

## Type:        string
193.174.240.7/32,192.168.42.127,tcp,1090
193.174.240.7/32,192.168.42.127,tcp,1091
193.174.240.7/32,192.168.42.127,tcp,1092
193.174.240.7/32,192.168.42.127,tcp,1093
193.174.240.7/32,192.168.42.127,tcp,1094
193.174.240.7/32,192.168.42.127,tcp,1095
193.174.240.7/32,192.168.42.127,tcp,1096
193.174.240.7/32,192.168.42.127,tcp,1097
193.174.240.7/32,192.168.42.127,tcp,1098
193.174.240.7/32,192.168.42.127,tcp,1099
"
Comment 1 Lars Müller 2010-08-14 20:54:13 UTC
Removing the

## Type:    string line

solved the issue.
Comment 2 Ludwig Nussel 2010-08-16 07:09:00 UTC
fillup "feature"

*** This bug has been marked as a duplicate of bug 340926 ***