From: Jérôme Magnin Date: Wed, 7 Feb 2018 10:39:58 +0000 (+0100) Subject: DOC: Describe routing impact of using interface keyword on bind lines X-Git-Tag: v1.9-dev1~430 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=61275198b30a505df7824ba9081d45d5d6d07f81;p=thirdparty%2Fhaproxy.git DOC: Describe routing impact of using interface keyword on bind lines --- diff --git a/doc/configuration.txt b/doc/configuration.txt index 89421dbbca..7cc5c13cea 100644 --- a/doc/configuration.txt +++ b/doc/configuration.txt @@ -10799,7 +10799,12 @@ interface interface, not an aliased interface. It is also possible to bind multiple frontends to the same address if they are bound to different interfaces. Note that binding to a network interface requires root privileges. This parameter - is only compatible with TCPv4/TCPv6 sockets. + is only compatible with TCPv4/TCPv6 sockets. When specified, return traffic + uses the same interface as inbound traffic, and its associated routing table, + even if there are explicit routes through different interfaces configured. + This can prove useful to address asymmetric routing issues when the same + client IP addresses need to be able to reach frontends hosted on different + interfaces. level This setting is used with the stats sockets only to restrict the nature of