peter 9c1da17e90 pf needs to be started after the network is up, because some pf rules ... derive IP address(es) from the interface (e.g "... from any to fxp0"). This however, creates window for possible attacks from the network. Implement the solution proposed by YAMAMOTO Takashi: Add /etc/defaults/pf.boot.conf and load it with the /etc/rc.d/pf_boot script before starting the network. People who don't like the default rules can override it with their own /etc/pf.boot.conf. The default rules have been obtained from OpenBSD. No objections on: tech-security		2005-08-23 12:12:56 +00:00
..
Makefile	Consistently use CONFIGFILES & CONFIGLINKS (which enable the 'configinstall'	2004-05-16 09:53:09 +00:00
NetBSD.dist	Adapted to the changes of grfinfo(1) MANSUBDIR (hp300). (thanks Klaus Klein)	2005-08-20 17:23:53 +00:00
special	pf needs to be started after the network is up, because some pf rules	2005-08-23 12:12:56 +00:00