From: Jason Ish Date: Tue, 1 Oct 2019 15:09:10 +0000 (-0600) Subject: doc/drop.log: mark as deprecated and scheduled to be removed X-Git-Tag: suricata-5.0.0~110 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=212252faf272ce364ad955b5a41a5240352f30e9;p=thirdparty%2Fsuricata.git doc/drop.log: mark as deprecated and scheduled to be removed Also make sure options are in sync with those in suricata.yaml. --- diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst index 2e8da4b4dd..2e5c29dc23 100644 --- a/doc/userguide/configuration/suricata-yaml.rst +++ b/doc/userguide/configuration/suricata-yaml.rst @@ -583,6 +583,9 @@ With this option it is possible to send all alert and event output to syslog. Drop.log, a line based information for dropped packets ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +.. note:: This output has been deprecated and will be removed by + June 2020. + If Suricata works in IPS mode, it can drop packets based on rules. Packets that are being dropped are saved in the drop.log file, a Netfilter log format. @@ -592,8 +595,11 @@ a Netfilter log format. - drop: enabled: yes #The option is enabled. filename: drop.log #The log-name of the file for dropped packets. - append: yes #If this option is set to yes, the last filled drop.log-file will not be - #overwritten while restarting Suricata. If set to 'no' the last filled drop.log file will be overwritten. + append: yes #If this option is set to yes, the last filled + #drop.log-file will not be overwritten while + #restarting Suricata. If set to 'no' the last + #filled drop.log file will be overwritten. + filetype: regular #regular, unis_stream, unix_dgram .. _suricata-yaml-file-store: