opnsense-src/sys/modules/ipfw/Makefile

# $FreeBSD$

.PATH: ${.CURDIR}/../../netpfil/ipfw

KMOD=	ipfw
SRCS=	ip_fw2.c ip_fw_pfil.c
SRCS+=	ip_fw_dynamic.c ip_fw_log.c
SRCS+=	ip_fw_sockopt.c ip_fw_table.c
SRCS+=	opt_inet.h opt_inet6.h opt_ipdivert.h opt_ipfw.h opt_ipsec.h

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-27 21:08:13 -04: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 08:03:02 -05:00
o Create directory sys/netpfil, where all packet filters should reside, and move there ipfw(4) and pf(4). o Move most modified parts of pf out of contrib. Actual movements: sys/contrib/pf/net/.c -> sys/netpfil/pf/ sys/contrib/pf/net/.h -> sys/net/ contrib/pf/pfctl/.c -> sbin/pfctl contrib/pf/pfctl/.h -> sbin/pfctl contrib/pf/pfctl/pfctl.8 -> sbin/pfctl contrib/pf/pfctl/.4 -> share/man/man4 contrib/pf/pfctl/.5 -> share/man/man5 sys/netinet/ipfw -> sys/netpfil/ipfw The arguable movement is pf/net/*.h -> sys/net. There are future plans to refactor pf includes, so I decided not to break things twice. Not modified bits of pf left in contrib: authpf, ftp-proxy, tftp-proxy, pflogd. The ipfw(4) movement is planned to be merged to stable/9, to make head and stable match. Discussed with: bz, luigi 2012-09-14 07:51:49 -04:00			`.PATH: ${.CURDIR}/../../netpfil/ipfw`
Use a consistent style and one much closer to the rest of /usr/src 2001-01-06 09:00:42 -05:00
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 00:30:52 -04:00			`KMOD= ipfw`
Revert the last change to sys/modules/ipfw/Makefile and fix a standalone module build in a better way. Silence from: andre MFC after: 3 days 2004-08-26 10:18:30 -04:00			`SRCS= ip_fw2.c ip_fw_pfil.c`
Do not build ip_fw_nat.c for ipfw.ko. It can be build as separate module. MFC after: 1 week 2011-03-29 02:42:52 -04:00			`SRCS+= ip_fw_dynamic.c ip_fw_log.c`
Now that ipfw is split into multiple files, we need to list them all in the Makefile for the module, otherwise it won't load due to missing symbols. The problem only affected head with ipfw built as a module. Reported by David Horn 2009-12-17 12:44:34 -05:00			`SRCS+= ip_fw_sockopt.c ip_fw_table.c`
Always use the opt_.h options for ipfw.ko, not just when compiled into the kernel. Do not try to build the module in case of no INET support but keep #error calls for now in case we would compile it into the kernel. This should fix an issue where the module would fail to enable IPv6 support from the rc framework, but also other INET and INET6 parts being silently compiled out without giving a warning in the module case. While here garbage collect unneeded opt_.h includes. opt_ipdn.h is not used anywhere but we need to leave the DUMMYNET entry in options for conditional inclusion in kernel so keep the file with the same name. Reported by: pluknet Reviewed by: plunket, jhb MFC After: 3 days 2011-11-04 12:24:19 -04:00			`SRCS+= opt_inet.h opt_inet6.h opt_ipdivert.h opt_ipfw.h opt_ipsec.h`
Use a consistent style and one much closer to the rest of /usr/src 2001-01-06 09:00:42 -05:00
No need to use a magic IPFIREWALL_MODULE - the build system supplies one already we can test for. 1999-04-20 10:31:23 -04: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 08:03:02 -05:00			`#`
Checking new lkm structure.. 1995-01-12 08:57:51 -05: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 08:03:02 -05: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 10:28:02 -04: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 08:03:02 -05:00			`#`
Add example for IPFIREWALL_DEFAULT_TO_ACCEPT 1997-09-10 00:19:07 -04: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 08:03:02 -05:00
Use .include <bsd.kmod.mk> to get to ../../*/conf/kmod.mk instead of encoding the relative path. 2000-05-26 21:14:33 -04:00			`.include <bsd.kmod.mk>`