freebsd-skq/sys/modules/ipfw/Makefile

# $FreeBSD$

.PATH: ${.CURDIR}/../../netinet

KMOD=	ipfw
SRCS=	ip_fw2.c

CFLAGS+= -DIPFIREWALL
#
#If you want it verbose
#CFLAGS+= -DIPFIREWALL_VERBOSE
#CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100
#
#If you want it to pass all packets by default
#CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT
#

.include <bsd.kmod.mk>
$Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00			`# $FreeBSD$`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 13:03:02 +00:00
Use a consistent style and one much closer to the rest of /usr/src 2001-01-06 14:00:42 +00:00			`.PATH: ${.CURDIR}/../../netinet`

Sample initial set of kld-ified modules. Not all have been completely converted yet. These are more of a starting point. This is NOT connected to the parent Makefile. OK'ed by jkh (who is ever so patiently waiting) 1998-10-16 04:30:52 +00:00			`KMOD= ipfw`
bring Makefile up to date with new ipfw Submitted by: luigi 2002-06-28 08:10:07 +00:00			`SRCS= ip_fw2.c`
Use a consistent style and one much closer to the rest of /usr/src 2001-01-06 14:00:42 +00:00
No need to use a magic IPFIREWALL_MODULE - the build system supplies one already we can test for. 1999-04-20 14:31:23 +00:00			`CFLAGS+= -DIPFIREWALL`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 13:03:02 +00:00			`#`
Checking new lkm structure.. 1995-01-12 13:57:51 +00:00			`#If you want it verbose`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 13:03:02 +00:00			`#CFLAGS+= -DIPFIREWALL_VERBOSE`
Use IPFIREWALL_MODULE instead of ACTUALLY_LKM_NOT_KERNEL to indicate LKM'ness. ACTUALLY_LKM_NOT_KERNEL is supposed to be so ugly that it only gets used until <machine/conf.h> goes away. bsd.kmod.mk should define a better-named general macro for this. Some places use PSEUDO_LKM. This is another bad name. Makefile: Added IPFIREWALL_VERBOSE_LIMIT option (commented out). 1996-06-23 14:28:02 +00:00			`#CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 13:03:02 +00:00			`#`
Add example for IPFIREWALL_DEFAULT_TO_ACCEPT 1997-09-10 04:19:07 +00:00			`#If you want it to pass all packets by default`
			`#CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT`
			`#`
Firewall can be used as lkm module.To use it firewall should NOT be compiled into kernel. Then it can be loaded.This is misc module but i'v got no problemms with it,so shouldn't you i suppose.. BTW this is very stupid to have one module in CVS for ALL lkm's... 1995-01-12 13:03:02 +00:00
Use .include <bsd.kmod.mk> to get to ../../*/conf/kmod.mk instead of encoding the relative path. 2000-05-27 01:14:33 +00:00			`.include <bsd.kmod.mk>`