mirror of
https://gitlab.com/shorewall/code.git
synced 2024-12-23 06:38:53 +01:00
Additional documentation changes.
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
a71b61c238
commit
c4f21ffefb
@ -371,6 +371,9 @@ ACCEPT - - tcp 135,139,445</programlisting>
|
||||
QUEUE_DEFAULT=none
|
||||
REJECT_DEFAULT="AllowICMPs,Broadcast(DROP),Multicast(DROP)"
|
||||
</programlisting>
|
||||
|
||||
<para>Note that in both cases, logging occurs based on the setting of
|
||||
LOG_LEVEL in shorewall[6].conf.</para>
|
||||
</section>
|
||||
|
||||
<section id="Defining">
|
||||
|
@ -266,7 +266,16 @@
|
||||
<para>You will need to change all instances of log levels (usually
|
||||
<quote>info</quote>) in your Shorewall configuration files to
|
||||
<quote>NFLOG</quote> - this includes entries in the policy, rules and
|
||||
shorewall.conf files. Here's what I had at one time:</para>
|
||||
shorewall.conf files. If you initially installed using Shorewall 5.1.2
|
||||
or later, you can simply change the setting of LOG_LEVEL in
|
||||
shorewall.conf.</para>
|
||||
|
||||
<para>Otherwise, you must search for all instances of log levels in your
|
||||
configuration and change them accordingly. If you currently run
|
||||
Shorewall 5.1.2 or later, then change them to $LOG_LEVEL and set
|
||||
LOG_LEVEL accordingly. If you are running an earlier release, using a
|
||||
shell variable simplifies future changes. Here's what I had at one
|
||||
time:</para>
|
||||
|
||||
<programlisting>gateway:/etc/shorewall# grep -v ^\# * | egrep '\$LOG|ULOG|LOGFILE'
|
||||
params:LOG=NFOG
|
||||
|
Loading…
Reference in New Issue
Block a user