Clean up the PF section on loading kernel modules.
- Give specific clear examples on how to load the pf module and the pflog module. - Remove some information that is stated in the section right above. - Update the doc to reflect that pflog is now its own module. [1] PR: 140896 [1]
This commit is contained in:
parent
85ceda6528
commit
6a33ba5dde
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=34974
1 changed files with 31 additions and 18 deletions
|
@ -236,20 +236,25 @@
|
|||
url="http://pf4freebsd.love2party.net/"></ulink>.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Using the PF loadable kernel module</title>
|
||||
<title>Using the PF loadable kernel modules</title>
|
||||
|
||||
<para>Since the release of &os; 5.3, PF has been included in the
|
||||
basic install as a separate run time loadable module. The
|
||||
system will dynamically load the PF kernel module when the
|
||||
&man.rc.conf.5; statement <literal>pf_enable="YES"</literal>
|
||||
is present. However, the <acronym>PF</acronym> module will
|
||||
not be loaded if the system cannot find a <acronym>PF</acronym>
|
||||
ruleset configuration file. The default location is
|
||||
<filename>/etc/pf.conf</filename>. If your
|
||||
<acronym>PF</acronym> ruleset is located somewhere else put
|
||||
<literal>pf_rules="<replaceable>/path/pf.rules</replaceable>"</literal>
|
||||
to your <filename>/etc/rc.conf</filename> configuration file to
|
||||
specify the location.</para>
|
||||
<para>To load the PF Kernel Module add the following line to
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>pf_enable="YES"</programlisting>
|
||||
|
||||
<para>Then run the startup script to load the module:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/etc/rc.d/pf start</userinput></screen>
|
||||
|
||||
<para>Note that the PF Module will not load if it cannot find
|
||||
the ruleset config file. The default location is
|
||||
<filename>/etc/pf.conf</filename>. If the PF ruleset is
|
||||
located somewhere else, PF can be instructed to look there by
|
||||
adding a line like the following to
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>pf_rules="<replaceable>/path/to/pf.conf</replaceable>"</programlisting>
|
||||
|
||||
<note>
|
||||
<para>As of &os; 7.0 the sample <filename>pf.conf</filename>
|
||||
|
@ -261,14 +266,22 @@
|
|||
</note>
|
||||
|
||||
<para>The <acronym>PF</acronym> module can also be loaded manually
|
||||
from the command line:</para>
|
||||
from the command line:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kldload pf.ko</userinput></screen>
|
||||
|
||||
<para>The loadable module was created with &man.pflog.4; enabled
|
||||
which provides support for logging. If you need other
|
||||
<acronym>PF</acronym> features you will need to compile
|
||||
<acronym>PF</acronym> support into the kernel.</para>
|
||||
<para>Logging support for PF is provided by the
|
||||
<literal>pflog.ko</literal> and can be loaded by adding the
|
||||
following line to <filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>pflog_enable="YES"</programlisting>
|
||||
|
||||
<para>Then run the startup script to load the module:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>/etc/rc.d/pflog start</userinput></screen>
|
||||
|
||||
<para>If you need other <acronym>PF</acronym> features you will
|
||||
need to compile <acronym>PF</acronym> support into the kernel.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
Loading…
Reference in a new issue