summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorcurrite <sll@disroot.org>2020-11-04 18:09:17 +0100
committercurrite <sll@disroot.org>2020-11-04 18:09:17 +0100
commita31185f89520300ae370e76bd72634d0239e505c (patch)
tree3e09adaf67020dacd0dffb2a8bcf88ea351bec4b
parent168247e76ad1b03e4d1dab2631ee970afeb74549 (diff)
downloadvyos-documentation-a31185f89520300ae370e76bd72634d0239e505c.tar.gz
vyos-documentation-a31185f89520300ae370e76bd72634d0239e505c.zip
wan-load-balancing: add wiki image for sticky connections
-rw-r--r--docs/_static/images/sticky-connections.jpgbin0 -> 22252 bytes
-rw-r--r--docs/load-balancing.rst6
2 files changed, 6 insertions, 0 deletions
diff --git a/docs/_static/images/sticky-connections.jpg b/docs/_static/images/sticky-connections.jpg
new file mode 100644
index 00000000..25fd72a9
--- /dev/null
+++ b/docs/_static/images/sticky-connections.jpg
Binary files differ
diff --git a/docs/load-balancing.rst b/docs/load-balancing.rst
index 07c18217..6b0bede9 100644
--- a/docs/load-balancing.rst
+++ b/docs/load-balancing.rst
@@ -159,6 +159,12 @@ This works through automatically generated source NAT (SNAT) rules, these rules
Sticky Connections
------------------
+Inbound connections to a WAN interface can be improperly handled when the reply is sent back to the client.
+
+.. image:: /_static/images/sticky-connections.jpg
+ :width: 80%
+ :align: center
+
Upon reception of an incoming packet, when a response is sent, it might be desired to ensure that it leaves from the same interface as the inbound one.
This can be achieved by enabling sticky connections in the load balancing: