Slackware 9.1 firewall box
 

I have following hardware (old server):

2 x CPU 233Mhz
384 Mb RAM
4 Gb IDE Hard disk
CD-ROM
Floppy
2 NIC's

I will try to get Slack into this machine, with the 2.4 kernel. I could skip XFree and only go for CL. What security packages (IPtables-based firewall, routing etc etc) are avaliable for Slack 9.1?

I did visit www.linuxpackages.net and noticed that Snort 2.0 was ready!

... OH, and another one - do you know of any ready-made iptables firewall-scripts that support 2 zones or a GUI tool that will make this easy (for Slackware)?

Well, you could always check out the packages listing at slackware.com - my favorite ftp server's here: ftp://ftp.cerias.purdue.edu/pub/os/s...1/PACKAGES.TXT. iptables is there, but I don't think anything else you'll need comes standard :-/

There are some decent firewall utilities knocking around...http://www.linuxquestions.org/questi...wall+graphical mentions a good number of them ^_^

cool,
Laura

guarddog
firewall builder
firestarter

Other assorted links:
http://www.linuxguruz.com/iptables/

---EDIT---
If you are planning on going without X, you won't be able to use any of the standard firewall GUI stuff. In that case, check out the netfilter . They have numerous HOWTOs and guides on building a firewall script from scratch. Make sure to checkout the frozen tux tutorial there as well. IMO, you will learn order of magnitude more about iptables and networking by doing it that way, rather than relying on a GUI to do it for you.

Hi,
there are many iptables script out there but in my opinion nothing fits a box better then your own script so I guess you should give a look at http:/www.netfilter.org documentation.
Snort is a great software so, yes, install it.
Keep an eye on the integrity of the FS. If you don't need great features but, you could use Integrit for this (not sure if there's a Slack package). It's easy to use and it just does what you need.
Once you're done with the iptables script, you might even try to do a check with Nessus. Not always so useful, but it can save your ass.

If you need a hand with iptables, well, I guess you're in the right place.

* * *
EDIT: for logging, I suggest syslog-ng. It allows you more control on where to write what