-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-10-17 at 00:37 +0200, Terje J. Hanssen wrote:
Carlos E. R. wrote:
In that case I would use profiles: one for home, another for the office.
On my multiboot homePC, SuseFirewall is undoubtly required as its connection to Internet is using a vanilla ADSL router (modem) and DHCP from my ISP. Booting Windows on the same PC, ZoneAlarm has been used correspondingly.
On my office, I'm not quite sure if SuseFirewall really is required on my Linux workstation there, as we have a separate Netsreen router with a built-in firewall to protect our Internet connection (cable modem now,
I would use the firewall anyway, but set up in the internal interface for the office, external at home. The profiles setup (office/home) can handle those changes automatically.
to be replaced with ADSL soon). The router port 22 and ssh service is forwarded now to the Linux workstation. What do you think, is SuseFirewall2 really needed for ssh/NX, though yet, it does of course not harm if I get it to work?
I don't know about "NX". :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFNg7XtTMYHG2NR9URAnKbAJ9V7FQ1KKqcAA+hQr+qfUJt3/7gigCeN89R Tblix8e4CKjBjcDw5YXHw/A= =2rXL -----END PGP SIGNATURE-----