From owner-freebsd-current Fri Jan 9 19:45:10 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA15022 for current-outgoing; Fri, 9 Jan 1998 19:45:10 -0800 (PST) (envelope-from owner-freebsd-current) Received: from nash.pr.mcs.net (nash.pr.mcs.net [204.95.47.72]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14972 for ; Fri, 9 Jan 1998 19:44:47 -0800 (PST) (envelope-from alex@nash.pr.mcs.net) Received: (from alex@localhost) by nash.pr.mcs.net (8.8.8/8.8.7) id VAA01085; Fri, 9 Jan 1998 21:39:20 -0600 (CST) (envelope-from alex) Message-Id: <199801100339.VAA01085@nash.pr.mcs.net> Date: Fri, 9 Jan 1998 21:39:19 -0600 (CST) From: Alex Nash Subject: Re: Firewall in kernel? To: thyerm@camtech.net.au cc: kong@kkk.ml.org, Studded@dal.net, current@FreeBSD.ORG In-Reply-To: <34B6DA80.C402491@camtech.net.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 10 Jan, Matthew Thyer wrote: > It is caused by a program in rc.network which trys to detect if the > firewall code is compiled into the kernel. This program fails in > some way and returns an error code in the 60's (I cant remember as > I'm having to use Win95 right now) but the script only expects > 0 or 1 as a return code so it mistakenly thinks the firewall is > in the kernel. Thanks for pointing this out! A few days ago I changed the error codes returned by ipfw to use those found in sysexits.h. I didn't realize there was a dependency on ipfw always returning 1 on error. The next CTM update will include a fix for this (the script, not ipfw :). Alex