os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Fixed invalid ipfstat command and markup with <command> when here anyway.

Browse source 
- Fixed capitalization when starting a new sentence. [1]
- Add missing ; in a few entities.
- Use manual page instead of man page.

Spotted by:	simon [1]
Approved by:	simon (mentor)
This commit is contained in:
Remko Lodder 2004-11-20 21:38:21 +00:00
parent 27de2ca6dc
commit 01ce6c4c72
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=22996
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -3342,7 +3342,7 @@ ipnat_rules="/etc/ipnat.rules" # rules definition file for ipnat</programlist
rules as the procedure can be executed as many times as needed. rules as the procedure can be executed as many times as needed.
</para> </para>
<para>See the &man.ipf.8; man page for details on the other flags <para>See the &man.ipf.8; manual page for details on the other flags
available with this command.</para> available with this command.</para>
<para>The &man.ipf.8; command expects the rules file to be a <para>The &man.ipf.8; command expects the rules file to be a
@ -3424,7 +3424,7 @@ ipnat_rules="/etc/ipnat.rules" # rules definition file for ipnat</programlist
you the ability to identify, drill down to, and see the you the ability to identify, drill down to, and see the
attacking packets. The optional sub-flags give the ability to attacking packets. The optional sub-flags give the ability to
select destination or source IP, port, protocol, you want to select destination or source IP, port, protocol, you want to
monitor in real time. See the &man.ipfstat.8 man page for monitor in real time. See the &man.ipfstat.8; manual page for
details.<para> details.<para>
</sect3> </sect3>
@ -3727,7 +3727,7 @@ sh /etc/ipf.rules.script</programlisting>
<para>The rule syntax presented here has been simplified to only <para>The rule syntax presented here has been simplified to only
address the modern stateful rule context and 'first matching address the modern stateful rule context and 'first matching
rule wins' logic. For the complete legacy rule syntax rule wins' logic. For the complete legacy rule syntax
description see the online ipf man page at &man.ipf.8</para> description see the online ipf manual page at &man.ipf.8;</para>
<para># is used to mark the start of a comment and may appear at <para># is used to mark the start of a comment and may appear at
the end of a rule line or on its own lines. Blank lines are the end of a rule line or on its own lines. Blank lines are
@ -4065,7 +4065,7 @@ sh /etc/ipf.rules.script</programlisting>
attacker would do.</para> attacker would do.</para>
<para>Any time you see log messages on a rule with .log first. <para>Any time you see log messages on a rule with .log first.
you should do an ipstat -h command to see the number of times You should do an <command>ipfstat -hio</command> command to see the number of times
the rule has been matched so you know if your are being the rule has been matched so you know if your are being
flooded, i.e. under attack.</para> flooded, i.e. under attack.</para>
@ -4376,7 +4376,7 @@ block in log first quick on dc0 all
<para>The rule syntax presented here has been simplified to <para>The rule syntax presented here has been simplified to
what is most commonly used in a non-commercial environment. what is most commonly used in a non-commercial environment.
For a complete rule syntax description see the man ipf page For a complete rule syntax description see the ipf manual page
at &man.ipnat.5;.</para> at &man.ipnat.5;.</para>
<para>The syntax for a <acronym>NAT</acronym> rule looks something like this: <para>The syntax for a <acronym>NAT</acronym> rule looks something like this:
@ -4840,7 +4840,7 @@ options IPV6FIREWALL_DEFAULT_TO_ACCEPT</programlisting>
<para>The rule syntax presented here has been simplified to <para>The rule syntax presented here has been simplified to
what is necessary to create a standard inclusive type what is necessary to create a standard inclusive type
firewall rule set. For a complete rule syntax description firewall rule set. For a complete rule syntax description
see the online &man.ipfw.8; man page.</para> see the online &man.ipfw.8; manual page.</para>
<para>Rules contain keywords, These keywords have to be coded <para>Rules contain keywords, These keywords have to be coded
in a specific order from left to right on the line. Keywords in a specific order from left to right on the line. Keywords