add to doc/pfring: Document additional cluster types

(cherry picked from commit 0ad6d4358f11d6d856f017726651182282b95281)

diff --git a/doc/userguide/configuration/suricata-yaml.rst b/doc/userguide/configuration/suricata-yaml.rst
index df466cb6109256b5f37b13821ce4de2eb8ad73e8..40430b52b8d98056501be83dc427fbd0f1bae39e 100644 (file)
--- a/doc/userguide/configuration/suricata-yaml.rst
+++ b/doc/userguide/configuration/suricata-yaml.rst
@@ -1919,6 +1919,9 @@ type value; in a round robin manner or a per flow manner that are part
 of the same cluster. All traffic for pf_ring will be load balanced across
 acquisition threads of the same cluster id.
 
+The "inner" flow means that the traffic will be load balanced based on
+address tuple after the outer vlan has been removed.
+
 +----------------------------+--------------------------------------------------+
 | Cluster Type               | Value                                            |
 +============================+==================================================+
@@ -1943,9 +1946,9 @@ of the same flow to the same thread. The flows itself will be
 distributed to the threads in a round-robin manner.
 
 If your deployment has VLANs, the cluster types with "inner" will use the innermost
-tuple for distribution.
+address tuple for distribution.
 
-Round-robin is not recommended with Suricata.
+The default cluster type is ``cluster_flow``; the ``cluster_round_robin`` is not recommended with Suricata.
 
 ::