compile option. All FreeBSD packet filters now use the PFIL_HOOKS API and
thus it becomes a standard part of the network stack.
If no hooks are connected the entire packet filter hooks section and related
activities are jumped over. This removes any performance impact if no hooks
are active.
Both OpenBSD and DragonFlyBSD have integrated PFIL_HOOKS permanently as well.
cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//'
BTW, what editors are the culprits? I'm using vim and it shows
me whitespace at EOL in troff files with a thick blue block...
Reviewed by: Silence from cvs diff -b
MFC after: 7 days
Remove the entire copy of ip_fw.h and just point readers at it as it
gets out of date..
Add mentions of dummynet and the fwd actions.
Still to do: Whoever did the 'stateful' stuff might mention it..
Use Dv and Va macros for defined values and variables,
respectively.
Use proper tag lists instead of approximations.
Use Xr for cross-references.
Make illegal sections legal subsections.
Use An and Aq to mark up author names and addresses,
Respectively.
standards and to clean up some of the English. The job is
nowhere complete.
This man page would be a good project for someone who knows
something about the firewall software, and would like to
contribute to the documentation effort. Many of the things
in this man page are out of date and do not reflect reality.
