June 18th, 2004, 07:11 AM
I have used slackware around 2 to 3 times but i have never really needed a firewall it seemed pretty well secure for what i needed to do. As almost all linux is.
June 18th, 2004, 11:35 AM
Donít know about ďcrapĒ, but just not flexible enough and just as hard or harder to learn then learning to write the rules by hand ( i.e. learning IPTables ) ... but then Iím a masochist and write my HTML ( now XHTML ) by hand too! If you can write the rulesets yourself you can use it on any distro.
Not a hardware firewall, or a "Linux Firewall Distro" Just a firewall you installed on a Slackware box and found to be good. The ones I find are usually just a front end for IPTables or something like that, which is fine, but they are also usually crap.
pooh sun tzu said
Looks interesting ... thanks, Iíll have to experiment with it when I get the time.
I use iptables as the ip packet filtering process (firewall) and firestarter as the front end gui configuration.
To my knowledge, not since kernel versions 2.0.* .
isn't IPFW available for linux?
see X/OS Experts in Open Systems BV
Last time I checked though, IPTables was able, if set up for it, to use old IPFWADM or IPChains rulesets. I have never tried it though and recall seeing somewhere that this may not be supported in the future, but I could be wrong on this.
Anyway, why would you want to revert back to IPFWADM or IPChains for that matter? IPFWADM had limitations on the protocols ( from Linux IP Firewalling Chains
and neither is Stateful.
The older Linux firewalling code doesn't deal with fragments, has 32-bit counters (on Intel at least), doesn't allow specification of protocols other than TCP, UDP or ICMP, can't make large changes atomically, can't specify inverse rules, has some quirks, and can be tough to manage (making it prone to user error).
" And maddest of all, to see life as it is and not as it should be" --Miguel Cervantes