* John Pettigrew; on 28 Oct, 2002 wrote:

comes with the Pro version of SuSE), try Shorewall (http://www.shorewall.net/). It's easier to set up and configure (IMO) and has preconfigured setups for 2-interface computers. Read the config instructions and you should only have to change a few lines in the config files. I'm afraid that the linux tools for connection sharing do require editing of config files - there's nothing as easy to set up as the Win programs, but you do get *vastly* more secure systems out of it!

Sorry to jump here but there is no such thing as "preconfigured firewall". Security is not IMO click "Yes" click "Accept" type of thing. I just had a look at the www.shorewall.net site especially for the so called preconfigured 2 interface and 3 interface setups. Looks to me there are many files that have to be configured (read edited with a text editor). SuSEfirewall2 has one (1) configuration file you can edited via text editor or via GUI ( YaST2 firewall module) so for Microsoft Windows GUI fans there is a GUI configurator for SuSEfirewall2 along with the explanation. The only thing that shorewall has as an extra benefit is there is a how to document. Yet SuSEfirewall2 has it also now http://prdownloads.sourceforge.net/susefaq/firewall2.pdf?download http://dinamizm.ath.cx/articles/firewall2.pdf ftp://dinamizm.ath.cx/documents/firewall2.pdf Yet IMHO SuSEfirewall2 is easier to setup while allowing real complex configurations. Just my 0.2 ¢ -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx

* John Pettigrew; on 28 Oct, 2002 wrote:

...

The only thing that shorewall has as an extra benefit is there is a how to document.

The end result is identical - a decent iptables firewall setup. As for tools, it's horses for courses. Shorewall is IMHO much better for those who don't know about iptables.

That these people who paid EUR 1,658.80 should switch to shorewall :-) http://www.suse.de/en/business/products/suse_business/firewall/customer_refe... http://www.suse.de/en/business/products/suse_business/firewall/prices.html -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx

Thank you all - I'm now successfully sharing my connection. Pretty straight forward - only 2 things to report: [1] I did decide to use SuSE's firewall in the end, and found it nice and easy - I would recommend this for newbies like myself, although I've not seen the Shorewall product which I'm sure is excellent too. [2] It only started working when I added DNS server entries on the Win machine's ethernet card TCP/IP settings - I used identical entries to the ones I found automatically set up on my Linux machine (the one with the internet connection on it) under domain servers in YAST2. Why is this? And have I done something lame that just happens to work by accident? Again, thanks all Andy On Mon, 2002-10-28 at 16:46, John Pettigrew wrote:

In a previous message, Togan Muftuoglu wrote:

...

* John Pettigrew; on 28 Oct, 2002 wrote:

...

Shorewall is IMHO much better for those who don't know about iptables.

That these people who paid EUR 1,658.80 should switch to shorewall :-)

? Don't get you. Big businesses (I hope) would have professionals who understand the details of the system to run their servers and firewalls. A very different market to the person I was addressing - a user who just wants to be able to set something up easily and quickly to protect their system.

Anyhow, I'm not trying to force anyone to like anything - I was just suggesting that someone might find Shorewall easier to set up than SuSEfirewall2.

John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

* andy stone; on 30 Oct, 2002 wrote:

[1] I did decide to use SuSE's firewall in the end, and found it nice and easy - I would recommend this for newbies like myself, although I've not seen the Shorewall product which I'm sure is excellent too.

Welcome on board :-)

[2] It only started working when I added DNS server entries on the Win machine's ethernet card TCP/IP settings - I used identical entries to the ones I found automatically set up on my Linux machine (the one with the internet connection on it) under domain servers in YAST2. Why is this? And have I done something lame that just happens to work by accident?

Well Although it is difficult to quess without knowing your config file, I'll take the stab On the firewall machine do you have a DNS server which is basicly forward and caching only ? If no then set that one first, and then for the configuration of other PC's in your local LAN use the ip of the firewall machine as DNS server. This will speed up the querries for example if your firewall machine has a local side ip as 192.168.1.1 then use this as the ip address. HTH -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx