-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2009-04-11 at 20:22 +0200, lynn wrote:
The configuration file (/etc/sysconfig/SuSEfirewall2) has inside lots of comments that explains what each option does. Did you read it?
Yep. When Yast failed I read it and tried everything I could before restoring my backup SuSEfirewall2 script and starting this thread.
I don't use Yast to configure the firewall, it is confusing.
I get the bit about FW_TRUSTED_NETS="192.168.1.4/32" opening all ports but strangely enough after I did that it only used 139
No, it uses more.
and finally connected with the firewall running. Security wise it doesn;t matter since it's just a NAS sitting beneath my televisor and it's behind my wireless router firewall anyway.
It matters if somebody gets in and uses that IP.
I'm just so glad I don't have to use Samba in the workplace. It seems so unpredictable. But then so does SuSEfirewall2. I'm disillusioned that something as simple as this has taken so long to understand.
The firewall is very simple! >:-)
BTW my NAS is a T50 from the Gallegos. It's a great idea but crippled by bugs in Busybox, out of date firmware, processor and lack of memory. For the price I could have got a little Acer with an hdmi port, AMD 64, 1024 memory and avoided all this Samba nonsense. They even look good too. Caveat E.
If you buy a popular NAS you also get updates, from the manufacturer or from the hacker community (hacker is not "bad", that would be "cracker"). But yes, they are expensive things.
Cheers and thanks for all your patience. L x
Welcome :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkng9c0ACgkQtTMYHG2NR9UFvwCgkxnxBSmlSq49GfbI5zuktRM9 WJgAn3ChEfDMBPzV4vj9y4+AqrecIp4m =Jst9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org