From owner-freebsd-security  Sun Jun 23 16:01:04 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA00278
          for security-outgoing; Sun, 23 Jun 1996 16:01:04 -0700 (PDT)
Received: from post.io.org (post.io.org [198.133.36.6])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA00270
          for <freebsd-security@FreeBSD.org>; Sun, 23 Jun 1996 16:00:59 -0700 (PDT)
Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA04886; Sun, 23 Jun 1996 18:53:39 -0400 (EDT)
Date: Sun, 23 Jun 1996 18:54:36 -0400 (EDT)
From: Brian Tao <taob@io.org>
To: "Andrew V. Stesin" <stesin@elvisti.kiev.ua>
cc: Darren Reed <avalon@coombs.anu.edu.au>, freebsd-security@FreeBSD.org
Subject: Re: IPFW vs. IP Filter?
In-Reply-To: <199606222305.CAA15185@office.elvisti.kiev.ua>
Message-ID: <Pine.NEB.3.92.960623185052.26828h-100000@zap.io.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-security@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 23 Jun 1996, Andrew V. Stesin wrote:
>
> Building IPfilter. Generally the instructions worked for me;
> I did minor modifications to the makefiles to suit my local
> needs.   Than cd FreeBSD; kinstall; cd BSD; make all install
> was the correct sequence, I recall.

    According to INSTALL.xBSD:


>>>>>
To build a kernel for use with the loadable kernel module, follow
these steps:

        1. do "make bsd"

        2. cd to the "BSD" directory and type "make install"

        3. run "4bsd/minstall" as root

        4. build a new kernel
[...]
<<<<<

    I can't get past the "make bsd" part:

# make bsd
[...]
gcc -I. -Wall -O -pipe -I.. -DIPFILTER_LKM -DIPFILTER_LOG -D`uname -m` -DINET -DKERNEL -D_KERNEL -I/usr/include -I/sys -I/sys/sys -I/sys/arch -DIPL_NAME=\"/dev/ipl\" -c ../mln_ipl.c -o ml_ipl.o
In file included from /usr/include/sys/conf.h:224,
                 from ../mln_ipl.c:14:
/usr/include/machine/conf.h:6: ioconf.h: No such file or directory
../mln_ipl.c:74: warning: initialization from incompatible pointer type
../mln_ipl.c:76: warning: initialization from incompatible pointer type
../mln_ipl.c:77: warning: initialization from incompatible pointer type
../mln_ipl.c:78: warning: initialization from incompatible pointer type
../mln_ipl.c:79: warning: initialization from incompatible pointer type
../mln_ipl.c:80: warning: initialization from incompatible pointer type
../mln_ipl.c:86: parse error before string constant
../mln_ipl.c:86: parse error before string constant
../mln_ipl.c:86: warning: missing braces around initializer for `IPL_VERSION_module.lkm_dev'
../mln_ipl.c:89: conflicting types for `cdevsw'
/usr/include/sys/conf.h:122: previous declaration of `cdevsw'
../mln_ipl.c: In function `ipl_load':
../mln_ipl.c:175: warning: suggest parentheses around assignment used as truth value
../mln_ipl.c: In function `xxxinit':
../mln_ipl.c:199: `_module' undeclared (first use this function)
../mln_ipl.c:199: (Each undeclared identifier is reported only once
../mln_ipl.c:199: for each function it appears in.)
../mln_ipl.c: At top level:
../mln_ipl.c:86: warning: `IPL_VERSION_module' defined but not used
*** Error code 1

Stop.
*** Error code 1

Stop.

    Do I have to unpack the source somewhere in the kernel source
tree?  ioconf.h only exists in the /sys/compile/[...] directories.
--
Brian Tao (BT300, taob@io.org, taob@ican.net)
Systems and Network Administrator, Internet Canada Corp.
"Though this be madness, yet there is method in't"