From 240c238f25b15c4121cd283292e2424243b7757a Mon Sep 17 00:00:00 2001 From: Jim Thompson Date: Sun, 20 Jan 2019 00:44:43 -0600 Subject: minor fixup in map doc (people -> seconds) Change-Id: I151c1afac2133ad32ad7779a59fffafee4b9de60 Signed-off-by: Jim Thompson --- src/plugins/map/map_doc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/plugins/map/map_doc.md b/src/plugins/map/map_doc.md index 17f3c51174b..f3e2a56706d 100644 --- a/src/plugins/map/map_doc.md +++ b/src/plugins/map/map_doc.md @@ -33,7 +33,7 @@ IPv4 and IPv6 virtual reassembly support the following configuration: map params reassembly [ip4 | ip6] [lifetime ] [pool-size ] [buffers ] [ht-ratio ] lifetime: - The time in milliseconds a reassembly structure is considered valid. The longer, the more reliable is reassembly, but the more likely it is to exhaust the pool of reassembly structures. IPv4 standard suggests a lifetime of 15 seconds. IPv6 specifies a lifetime of 60 people. Those values are not realistic for high-throughput cases. + The time in milliseconds a reassembly structure is considered valid. The longer, the more reliable is reassembly, but the more likely it is to exhaust the pool of reassembly structures. IPv4 standard suggests a lifetime of 15 seconds. IPv6 specifies a lifetime of 60 seconds. Those values are not realistic for high-throughput cases. buffers: The upper limit of buffers that are allowed to be cached. It can be used to protect against fragmentation attacks which would aim to exhaust the global buffers pool. -- cgit 1.2.3-korg