Editors Note:
This paragraph written by Michael W. Lucas, was a lead into to a nice testimonial for a PFsense firewall. For anybody that is in the IT consulting this first part is classic Dilbert.
Found in pfsense.org
My friends and co-workers know that I build firewalls. At least once a month someone says “My company needs a firewall with X and Y, and the price quotes I’ve gotten are tens of thousands of dollars. Can you help us out?”
Anyone who builds firewalls knows this question could be more realistically phrased as “Could you please come over one evening and slap together some equipment for me, then let me randomly interrupt you for the next three to five years to have you install new features, debug problems, set up features I didn’t know enough to request, attend meetings to resolve problems that can’t possibly be firewall issues but someone thinks might be the firewall, and identify solutions for my innumerable unknown requirements? Oh, and be sure to test every possible use case before deploying anything.
Like this:
Like Loading...
NetEqualizer News Blog
What does it take to build a firewall.
November 11, 2009 — netequalizerEditors Note:
This paragraph written by Michael W. Lucas, was a lead into to a nice testimonial for a PFsense firewall. For anybody that is in the IT consulting this first part is classic Dilbert.
Found in pfsense.org
My friends and co-workers know that I build firewalls. At least once a month someone says “My company needs a firewall with X and Y, and the price quotes I’ve gotten are tens of thousands of dollars. Can you help us out?”
Anyone who builds firewalls knows this question could be more realistically phrased as “Could you please come over one evening and slap together some equipment for me, then let me randomly interrupt you for the next three to five years to have you install new features, debug problems, set up features I didn’t know enough to request, attend meetings to resolve problems that can’t possibly be firewall issues but someone thinks might be the firewall, and identify solutions for my innumerable unknown requirements? Oh, and be sure to test every possible use case before deploying anything.
Share this:
Like this: