From owner-freebsd-current Sat Aug 31 05:43:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA11828 for current-outgoing; Sat, 31 Aug 1996 05:43:15 -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 FAA11821 for ; Sat, 31 Aug 1996 05:43:13 -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 HAA15696; Sat, 31 Aug 1996 07:43:12 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.13) id ; Sat, 31 Aug 96 07:43 CDT Date: Sat, 31 Aug 1996 07:43:11 -0500 (CDT) From: Alex Nash X-Sender: nash@Venus.mcs.com To: Ollivier Robert cc: "FreeBSD Current Users' list" Subject: Re: IPFW changes In-Reply-To: <199608310949.LAA00327@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Can anyone tell me what changed in IPFW between Aug, 18th and now ? Nothing. > I just rebooted after "make world" and ipfw rejected one the following > rules (without telling me the one but I know it is the first one): > > [...] > > 201 [11:45] root@keltia:~# ipfw add deny all from 127.0.0.0/8 to 0/0 via ppp0 > ipfw: ERROR - ip number > > It seems that neither "all" nor "ip" is recognized after the "deny"... 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". Now the question is: Is it legal to call the resolver with an address of 0? I thought that the default action in such cases is to append ".0"'s to the end of the address until you had a 32-bit address. Alex