https://bugzilla.novell.com/show_bug.cgi?id=811188
https://bugzilla.novell.com/show_bug.cgi?id=811188#c5
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |jsmeix@suse.com
Component|Printing |YaST2
InfoProvider|dpbasti@wp.pl |
AssignedTo|jsmeix@suse.com |locilka@suse.com
Summary|adding cups to allowed |yast2-firewall: system
|services in the firewall |unaccessible via interface
|does not allow broadcasting |in internal zone
QAContact|jsmeix@suse.com |jsrain@suse.com
--- Comment #5 from Johannes Meixner 2013-04-05 12:31:10 CEST ---
Having the interface for the trusted network in the internal zone
worked all the time for me and it still works for me under openSUSE 12.3
but only if I set up SuSEfirewall2 manually and
not with the YaST firewall module.
When I run the YaST firewall module and therein I only set
my interface "eth0" (the only existing interface except "lo")
to be in the internal zone (I leave all other settings as defaults)
and let the YaST firewall module start SuSEfirewall2,
then I can no longer access this machine in any way
via network (my ssh session on a remote host hangs
and it even does no longer respond to a "ping").
In particular CUPS browsing information from remote
CUPS servers cannot come in.
In contrast when I start SuSEfirewall2 manually as root using
# /sbin/SuSEfirewall2 start
it works as it did all the time in the past.
In particular I get CUPS browsing information from remote CUPS
servers via "eth0" with this interface in the internal zone.
Therefore the issue is likely a bug in the YaST firewall module
or perhaps in a lower level YaST functionality that is reladed
to starting and stopping services, compare bnc#800492
My openSUSE 12.3 system it up to date:
-----------------------------------------------------------------------------
# zypper -v update
Verbosity: 1
Initialising Target
Checking whether to refresh metadata for openSUSE-12.3-Non-Oss
Checking whether to refresh metadata for openSUSE-12.3-Oss
Checking whether to refresh metadata for openSUSE-12.3-Update
Checking whether to refresh metadata for openSUSE-12.3-Update-Non-Oss
Loading repository data...
Reading installed packages...
Force resolution: No
Nothing to do.
-----------------------------------------------------------------------------
I re-assign it to the maintainer of the YaST firewall module
for further analysis what exactly goes wrong in YaST here.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.