SuseFirewall2 setup for P2P Home Network?

I have a home network consisting of a DSL modem, feeding a Linksys
Router (with Firewall active), and three home computers running windows
connected to the Router.

I recently installed Suse Linux 9.3 on one computer and am having
difficulty learning how to set up the SuseFirewall2 to allow file and
printer sharing on the home network.

During the installation process, the firewall was setup automatically,
with network card setup for External network. Connection to the Internet
works well, but unless I disable the firewall, I can not access my home
network, and vice versa.

Can anyone point me to a site where this Linux newby can read
instructions on how to configure my SuseFirewall2 to allow an open P2P home
network, while still providing a layer of security to the Internet?


Thanks.

Ed

On Thu, 04 Aug 2005 22:10:58 GMT, Ed <Huckleberry_REMOVE_@bigvalley.net> wrote:
>
> I have a home network consisting of a DSL modem, feeding a Linksys
> Router (with Firewall active), and three home computers running windows
> connected to the Router.
>
> I recently installed Suse Linux 9.3 on one computer and am having
> difficulty learning how to set up the SuseFirewall2 to allow file and
> printer sharing on the home network.
>
> During the installation process, the firewall was setup automatically,
> with network card setup for External network. Connection to the Internet
> works well, but unless I disable the firewall, I can not access my home
> network, and vice versa.
>
> Can anyone point me to a site where this Linux newby can read
> instructions on how to configure my SuseFirewall2 to allow an open P2P home
> network, while still providing a layer of security to the Internet?

I don't know if Win file/printer sharing uses any ports besides netbios
ports (I do Linux with PuTTY, but I don't do Windows with Linux), but in
/etc/sysconfig/SuSEfirewall2 try setting the following variable:

FW_SERVICES_EXT_TCP="137:139"

Or to allow any local access maybe it would be safer to just list your
private LAN network as trusted like:

FW_TRUSTED_NETS="192.168.1.0/24"

> FW_SERVICES_EXT_TCP="137:139"
>
> Or to allow any local access maybe it would be safer to just list your
> private LAN network as trusted like:
>
> FW_TRUSTED_NETS="192.168.1.0/24"
>


With what little Linux knowledge I have, those two suggestions still
look good. I will see what happens by trying that in a bit.


Thanks.

Ed