From owner-freebsd-stable Tue Dec 2 09:56:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18667 for stable-outgoing; Tue, 2 Dec 1997 09:56:45 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18662 for ; Tue, 2 Dec 1997 09:56:43 -0800 (PST) (envelope-from nash@Venus.mcs.net) Received: from Venus.mcs.net (nash@Venus.mcs.net [192.160.127.92]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA02731; Tue, 2 Dec 1997 11:56:42 -0600 (CST) Received: from localhost (nash@localhost) by Venus.mcs.net (8.8.7/8.8.2) with SMTP id LAA09566; Tue, 2 Dec 1997 11:56:42 -0600 (CST) Date: Tue, 2 Dec 1997 11:56:41 -0600 (CST) From: Alex Nash To: Dan Jacobowitz cc: freebsd-stable@freebsd.org Subject: Re: ipfw between kernel versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Dec 1997, Dan Jacobowitz wrote: > I just attempted to upgrade a 2.2.2 machine to 2.2.5 kernel, and I ran > into a little problem. As near as I have been able to tell, the ipfw > ioctl's changed between the two, causing ipfw to fail and not put in place > the allow all rules needed to counter the default policy - thus no > network. > > Is my interpretation of this correct? Should I just install 2.2.5 ipfw? Installing 2.2.5 ipfw would be enough to fix the problem. But you're better off remaking everything. > (I'm going to make installworld after I get the kernel in, but based on > past experience I want to do those two seperately.) > > Will the 2.2.5 ipfw work with a 2.2.2 kernel at all? 2.2.5 ipfw will not work with 2.2.2-RELEASE kernels, but will work with 2.2.2-STABLE after August 21st. Alex