diff options
| author |   Jim Thompson <jim@netgate.com> | 2019-01-20 00:44:43 -0600 |
|---|---|---|
| committer | Jim Thompson <jim@netgate.com> | 2019-01-20 00:44:43 -0600 |
| commit | 240c238f25b15c4121cd283292e2424243b7757a (patch) | |
| tree | 433b5954677ec038fd7eda3b010c3e7da811b947 | |
| parent | 0702554639e5149d9012cc196aa43c3c8d0d7f9b (diff) | |
minor fixup in map doc (people -> seconds)
Change-Id: I151c1afac2133ad32ad7779a59fffafee4b9de60
Signed-off-by: Jim Thompson <jim@netgate.com>
| -rw-r--r-- | src/plugins/map/map_doc.md | 2 |
1 files changed, 1 insertions, 1 deletions
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 <lifetime-ms>] [pool-size <pool-size>] [buffers <buffers>] [ht-ratio <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. |