From owner-freebsd-current@FreeBSD.ORG Tue Jun 10 05:34:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 031C737B401 for ; Tue, 10 Jun 2003 05:34:10 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BD3143F3F for ; Tue, 10 Jun 2003 05:34:09 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) h5ACY8AQ091012; Tue, 10 Jun 2003 08:34:08 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)h5ACY8WL091009; Tue, 10 Jun 2003 08:34:08 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 10 Jun 2003 08:34:08 -0400 (EDT) From: Andre Guibert de Bruet To: Ian Freislich In-Reply-To: <4741.1055245990@mci.com> Message-ID: <20030610083242.S56112@alpha.siliconlandmark.com> References: <3EE5B9D5.8FE3E6EF@mindspring.com> <4741.1055245990@mci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: New Kernel Breaks IPFW X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 12:34:10 -0000 Ian, The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ > On Tue, 10 Jun 2003, Ian Freislich wrote: > Terry Lambert wrote: > > Apparently, someone hosed the compiler flags. Looking at your > > cribbed link: > > > > > Someone posted a link to the failure that I get, so I'll crib: > > > http://www.0xfce3.net/error.txt > > > > We see: > > > > cc -O -pipe -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include > > -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o xinstall xinstall.o -legacy > > > > Works. > > > > cc -O -pipe -I. -I/usr/src/usr.sbin/config -W -Wall -ansi -pedantic > > -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Winline > > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls > > -Wshadow -Wstrict-prototypes -Wwrite-strings -std=iso9899:1999 > > -I/usr/obj/usr/src/i386/legacy/usr/include -c config.c > > Hmmm, BDEFLAGS. config.c appears to compile without them. > > > > > Short term, cd /usr/src/sbin/ipfw; make depend && make all install ought > > > > to fix it. > > > > > > I tried that as well, but the new binary also dumps core, but works > > > well with previous versions of the firewall. Even back as far as > > > my kernel.working from May 7 2003. > > > > Bogus header files; specifically, . Because you > > can't build world, you are compiling the ipfw program with the old > > system include files instead of the new ones. You may also be > > missing a cvs update on the ipfw sources themselves (specifically, > > ipfw2.c). > > No, it did compile ipfw2.c (r1.24). I also installed all new > includes before I compiled ipfw and re-worlding to no avail. I > figured an old kernel with a working firewall was better than a new > kernel with no firewall. > > Ian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >