Linked by Thom Holwerda on Wed 15th Sep 2010 14:27 UTC, submitted by Ed
Thread beginning with comment 441517
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: GUI interface needed
by sorpigal on Fri 17th Sep 2010 21:56
in reply to "RE: GUI interface needed"
RE[3]: GUI interface needed
by phoenix on Fri 17th Sep 2010 22:59
in reply to "RE[2]: GUI interface needed"
If the MCSE doesn't know enough about networking to understand English sentences (allow protocol from subnet to subnet in recv interface), then they have no business being anywhere near a firewall, let alone a network server of any kind.
A well-documented text file is a heck of a lot easier to understand than a bunch of icons and arrows onscreen.





Member since:
2008-10-30
If you need a GUI to configure a firewall, the *BSD operating systems really aren't for you.
Firestarter is a poor excuse for a firewall frontend and Guarddog is a complete joke that is lacking many features. These are fine on simple home machines, as that is their intended use, but no knowledgeable system admin would use them on a server. Any good Linux admin would use iptables, from the command line, because of the sheer control the command line allows when compared to a limiting GUI application.
Both FreeBSD and OpenBSD provide excellent documentation for configuring IPFW/PF, especially when compared to iptables on Linux. All that is required by the end user is a little reading and the ability to follow instructions. If you cannot do this, you have no reason to be administrating such a complex firewall to begin with.
Writing firewall rules in a configuration file is not the same as programming by any stretch of the imagination. Using your logic, it could be reasoned that no end user could ever configure a hard drive mount because "programming" /etc/fstab is just too difficult. Please.