src/sbin/ipfw/ipfw.8, branch release/4.0.0_cvs

This commit was manufactured by cvs2svn to create tag

2000-03-20T08:47:53+00:00

'RELENG_4_0_0_RELEASE'.

This commit was manufactured to restore the state of the 4.0-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

A huge rewrite of the manual page (mostly -mdoc related).

2000-02-28T15:21:12+00:00

Reviewed by:	luigi, sheldonh

Support and document new stateful ipfw features.

2000-02-10T14:25:26+00:00

Approved-by: jordan

Support per-flow queueing in dummynet.

2000-01-08T11:19:19+00:00

Implement masks on UDP/TCP ports.
Large rewrite of the manpage.

Work supported by Akamba Corp.

Turn on 'ipfw tee'. Update man page. Please note (from the man page):

1999-12-06T01:00:24+00:00

    Packets that match a tee rule should not be immediately accepted,
    but should continue going through the rule list.  This may be fixed
    in a later version.

I hope to fix this soon in a separate commit.

Remove one obsoleted entry from the BUGS section.

1999-10-20T12:59:35+00:00

$Id$ -> $FreeBSD$

1999-08-28T00:22:10+00:00

To christen the brand new security category for syslog, we get IPFW

1999-08-21T18:35:55+00:00

using syslog(3) (log(9)) for its various purposes! This long-awaited
change also includes such nice things as:
	* macros expanding into _two_ comma-delimited arguments!
	* snprintf!
	* more snprintf!
	* linting and criticism by more people than you can shake a stick at!
	* a slightly more uniform message style than before!
	 and last but not least
	* no less than 5 rewrites!

Reviewed by:	committers

Userland and manual page changes for probabilistic rule match.

1999-08-11T15:36:13+00:00

Because the kernel change was done in a backward-compatible way,
you don't need to recompile ipfw if you don't want to use the new
feature.

Make ipfw's logging more dynamic. Now, log will use the default limit

1999-08-01T16:57:24+00:00

_or_ you may specify "log logamount number" to set logging specifically
the rule.
   In addition, "ipfw resetlog" has been added, which will reset the
logging counters on any/all rule(s). ipfw resetlog does not affect
the packet/byte counters (as ipfw reset does), and is the only "set"
command that can be run at securelevel >= 3.
   This should address complaints about not being able to set logging
amounts, not being able to restart logging at a high securelevel,
and not being able to just reset logging without resetting all of the
counters in a rule.