From owner-freebsd-current  Sat Aug 31 10:30:48 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA01063
          for current-outgoing; Sat, 31 Aug 1996 10:30:48 -0700 (PDT)
Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA01058
          for <freebsd-current@FreeBSD.org>; Sat, 31 Aug 1996 10:30:46 -0700 (PDT)
Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id MAA22745; Sat, 31 Aug 1996 12:30:45 -0500 (CDT)
Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.13)
	id <m0uwtsa-000IDOC@venus.mcs.com>; Sat, 31 Aug 96 12:30 CDT
Date: Sat, 31 Aug 1996 12:30:44 -0500 (CDT)
From: Alex Nash <nash@mcs.net>
X-Sender: nash@Venus.mcs.com
To: Ollivier Robert <roberto@keltia.freenix.fr>
cc: "FreeBSD Current Users' list" <freebsd-current@FreeBSD.org>
Subject: Re: IPFW changes
In-Reply-To: <199608311655.SAA01875@keltia.freenix.fr>
Message-ID: <Pine.BSI.3.91.960831122415.14043C-100000@Venus.mcs.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 31 Aug 1996, Ollivier Robert wrote:

> According to Alex Nash:
> > ipfw is complaining that it can't resolve the address '0' which is
> > being caused by the newly merged bind-4.9.4-P1 resolver (merged in 3
> > days ago).  For the time being, use the "any" keyword instead of
> > "0/0".
> 
> OK, that's working now.
> 
> Another question, why the sysctl variables for IPFW not there ?

This was on my TODO list from several months ago :(  Any sysctl experts 
out there want to give this a shot?

Alex