http://qa.mandrakesoft.com/show_bug.cgi?id=4697
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From [EMAIL PROTECTED] 2003-12-08 14:03 -------
I am not sure that "SMB" is the best choice, when other options are "Domain Name
Server". Maybe "Windows Networking (SMB/CIFS)" would be better.
Also, the whole design of drakfirewall ignores the fact that linux servers in
small offices often do internet connection sharing *and* other services, so it
would be nice if drakfirewall could allow the admin to allow SMB traffic to the
internal network and not to the external network ... it's not a good idea to
have it open the same services on both sides ...
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
Mandrake is frequently used as a SMB server with use of Samba.
The list of ports that need to be passed through for the SMB protocol to work
lists 4 ports, and it's not very easy to find this list on the Internet.
Those ports are:
137/udp
138/udp
139/tcp
445/tcp
So anyone who would like to open SMB using drakfirewall, would have to click
"advanced" and type:
137/udp 138/udp 139/tcp 445/tcp
This is far from intuitive of course, even for advanced power-users who want a
personal firewall on their workstation and filesharing with Windows at the same
time.
I propose that an additional checkbox be added to drakfirewall, "SMB", that
opens those 4 ports on the firewall.
