From owner-freebsd-security  Thu Apr 24 09:29:34 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA15095
          for security-outgoing; Thu, 24 Apr 1997 09:29:34 -0700 (PDT)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA15087;
          Thu, 24 Apr 1997 09:29:30 -0700 (PDT)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA08107;
	Thu, 24 Apr 1997 09:28:36 -0700 (PDT)
Date: Thu, 24 Apr 1997 09:28:36 -0700 (PDT)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199704241628.JAA08107@biggusdiskus.flyingfox.com>
To: freebsd-isp@freebsd.org, mike@sentex.net, security@freebsd.org
Subject: Re: Commercial vs built in firewall capabilities of FreeBSD
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Part of what you're buying in a commercial firewall is expertise:
packaged implicitly in the product, ongoing support services, and
in some cases, bundled consulting services with firewall setup.

Yes, you can roll a pretty good firewall with FreeBSD, socksv5,
ssh, etc.  It just takes some expertise and time.  Whether you're
better off spending that (assuming you have it), or spending the
money for a commercial product, is purely a business decision.

Jim Shankland
Flying Fox Computer Systems, Inc.