From d4eaf157ee8b96694598ccb195b5b82cd455930e Mon Sep 17 00:00:00 2001 From: Denis Peplin Date: Wed, 9 Mar 2005 11:43:14 +0000 Subject: [PATCH] Note: ... -> ... , and align according this change No other content changes --- .../books/handbook/firewalls/chapter.sgml | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml b/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml index c80e44627d..ae98fe7afd 100644 --- a/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml @@ -2477,11 +2477,15 @@ options IPV6FIREWALL_DEFAULT_TO_ACCEPT zero removes the logging limit. Once the limit is reached, logging can be re-enabled by clearing the logging counter or the packet counter for that rule, see - the ipfw reset log command. Note: logging is done after - all other packet matching conditions have been - successfully verified, and before performing the final - action (accept, deny) on the packet. It is up to you to - decide which rules you want to enable logging on. + the ipfw reset log command. + + + Logging is done after + all other packet matching conditions have been + successfully verified, and before performing the final + action (accept, deny) on the packet. It is up to you to + decide which rules you want to enable logging on. +