http://qa.mandrakesoft.com/show_bug.cgi?id=4697
------- Additional Comments From [EMAIL PROTECTED] 2003-22-10 00:57 ------- Just found on http://www.shorewall.net/samba.htm: If the firewall needs to be able to act as a SMB client, including discovery (e.g. with LinNeighborhood or Gnomba), additional changes need to be done in order to make SMB clients work on the firewalled machine. Only after I've added the following lines to the "rules" file I could browser the network neighborhood: ACCEPT fw net udp 1024: 137 ACCEPT net fw udp 1024: 137 -- 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.
