[DOC] document IPv6 support for stick-tables

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 3ebbb471c75e128557f141420e3df282a6890e97..5d93f767f7831bbb55339f2a6fc42724a00efa68 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -5507,6 +5507,11 @@ stick-table type {ip | integer | string [len <length>] | binary [len <length>]}
                very fast entry lookup and stores with almost no overhead. This
                is mainly used to store client source IP addresses.
 
+    ipv6       a table declared with "type ipv6" will only store IPv6 addresses.
+               This form is very compact (about 60 bytes per entry) and allows
+               very fast entry lookup and stores with almost no overhead. This
+               is mainly used to store client source IP addresses.
+
     integer    a table declared with "type integer" will store 32bit integers
                which can represent a client identifier found in a request for
                instance.
@@ -7817,12 +7822,24 @@ equivalent used in ACLs.
 The list of currently supported pattern fetch functions is the following :
 
   src          This is the source IPv4 address of the client of the session.
-               It is of type IP and only works with such tables.
+               It is of type IPv4 and works on both IPv4 and IPv6 tables.
+               On IPv6 tables, IPv4 address is mapped to its IPv6 equivalent,
+               according to RFC 4291.
+
+  src6         This is the source IPv6 address of the client of the session.
+               It is of type IPv6 and only works with such tables.
 
   dst          This is the destination IPv4 address of the session on the
                client side, which is the address the client connected to.
                It can be useful when running in transparent mode. It is of
-               typie IP and only works with such tables.
+               type IPv4 and works on both IPv4 and IPv6 tables.
+               On IPv6 tables, IPv4 address is mapped to its IPv6 equivalent,
+               according to RFC 4291.
+
+  dst6         This is the destination IPv6 address of the session on the
+               client side, which is the address the client connected to.
+               It can be useful when running in transparent mode. It is of
+               typie IPv6 and only works with such tables.
 
   dst_port     This is the destination TCP port of the session on the client
                side, which is the port the client connected to. This might be