https://bugzilla.novell.com/show_bug.cgi?id=462307
User swerdna@opensuse-forums.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=462307#c1
--- Comment #1 from John Andrews 2008-12-29 21:44:04 MST ---
Leave broadcasts and the connection tracker engine out of consideration for
this bug -- they aren't the issue here. I've found the issue and lay it out for
you below:
I have checked the text file /etc/sysconfig/SuSEfirewall2 more closely between
10.2, 11.0 and 11.3 to see what is different when the Samba Server tool
(located at Yast --> Security and Users --> Allowed Services -->add Samba
Server) is used.
In 10.3 and 11.0 the tool causes port designations to be added to the lines
FW_SERVICES_EXT_TCP and FW_SERVICES_EXT_TCP and FW_ALLOW_FW_BROADCAST_EXT.
In 11.1 a new approach is used. The tool no longer causes port assignment
similar to 10.x, 11.1. Instead it causes the term "samba-server" to be added to
the line FW_CONFIGURATIONS_EXT (similar to the way apache and ssh are treated).
Putting that phrase in that line doesn't cause any firewall effect yet for
Samba and that's where the fix-it focus should be.
--
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.