From owner-freebsd-security Wed Jul 5 14: 9:57 2000 Delivered-To: freebsd-security@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C705C37C163 for ; Wed, 5 Jul 2000 14:09:53 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id A0EFB1C64; Wed, 5 Jul 2000 17:09:52 -0400 (EDT) Date: Wed, 5 Jul 2000 17:09:52 -0400 From: Bill Fumerola To: Chris Dillon Cc: openzero@bsdmail.com, freebsd-security@FreeBSD.ORG Subject: Re: Firewalls and the endless story! Message-ID: <20000705170952.O4034@jade.chc-chimes.com> References: <20000705202937.64113.qmail@bsdmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Wed, Jul 05, 2000 at 03:57:22PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 05, 2000 at 03:57:22PM -0500, Chris Dillon wrote: > > After posting, for some help with my sucky fireball > > I upgraded from FreeBSD-2.2.8-RELEASE to FreeBSD-3.4-RELEASE > > + SecureBSD1.0, in hope it will work now. > > > > But nothing happends! The firewall doesn't work > > and FreeBSD-3.4 (and 4.0) is a boring unstable > > system! > > Hardly. I have no problems using FreeBSD 3.x or 4.x in any of the > many systems I use them in, including a large firewall. Yes, and the original poster demonstrated even further stupidity by adding a proprietary product (SecureBSD 1.0) into the mix and then expect that we support it. "Works for me." -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message