From: Victor Julien Date: Thu, 3 Oct 2019 13:37:37 +0000 (+0200) Subject: stream: remove fix stream.depth references X-Git-Tag: suricata-5.0.0~120 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=be6cdd37f85de9c026f385cad48d4a9617923584;p=thirdparty%2Fsuricata.git stream: remove fix stream.depth references --- diff --git a/doc/userguide/performance/tuning-considerations.rst b/doc/userguide/performance/tuning-considerations.rst index 958877c112..78bd6e0860 100644 --- a/doc/userguide/performance/tuning-considerations.rst +++ b/doc/userguide/performance/tuning-considerations.rst @@ -129,4 +129,4 @@ In the example below: toclient-chunk-size: 2560 randomize-chunk-size: yes -Inspection will be skipped when ``stream.depth`` of 1mb is reached for a particular flow. +Inspection will be skipped when ``stream.reassembly.depth`` of 1mb is reached for a particular flow. diff --git a/doc/userguide/rules/file-keywords.rst b/doc/userguide/rules/file-keywords.rst index f6d9258630..ede6ba65ce 100644 --- a/doc/userguide/rules/file-keywords.rst +++ b/doc/userguide/rules/file-keywords.rst @@ -178,7 +178,7 @@ Examples:: filesize:<100MB; # smaller than 100 megabytes **Note**: For files that are not completely tracked because of packet -loss or stream.depth being reached on the "greater than" is +loss or stream.reassembly.depth being reached on the "greater than" is checked. This is because Suricata can know a file is bigger than a value (it has seen some of it already), but it can't know if the final size would have been within a range, an exact value or smaller than a diff --git a/suricata.yaml.in b/suricata.yaml.in index a617b00ae3..4a19b43cbb 100644 --- a/suricata.yaml.in +++ b/suricata.yaml.in @@ -568,7 +568,7 @@ outputs: # 2 files per TCP session and stores the raw TCP data into them. # Using 'both' will enable both file and dir modes. # - # Note: limited by stream.depth + # Note: limited by stream.reassembly.depth - tcp-data: enabled: no type: file @@ -1345,7 +1345,7 @@ flow-timeouts: # inline: no # stream inline mode # drop-invalid: yes # in inline mode, drop packets that are invalid with regards to streaming engine # max-synack-queued: 5 # Max different SYN/ACKs to queue -# bypass: no # Bypass packets when stream.depth is reached. +# bypass: no # Bypass packets when stream.reassembly.depth is reached. # # Warning: first side to reach this triggers # # the bypass. #