mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-08-07 15:47:01 +02:00
Code Issues Projects Releases Wiki Activity

DOC: quic: fix recommandation for bind on multiple address

Browse Source 
Documentation falsely mentions that binding on multiple addresses is
forbidden for QUIC listeners. This is not the case. Moreover, this
behavior is reliable when using destination address retrieval on receive
via IP_PKTINFO, which allows to determine the proper source address for
response.

This should be backported up to 2.7. On 2.6 specific source address
definition on sendmsg via IP_PKTINFO is not implemented. As such, bind
on multiple addresses should remain forbidden for this release.
This commit is contained in:
Amaury Denoyelle 2024-02-15 18:43:44 +01:00
parent ee88c4418f
commit f01ae9f075
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/configuration.txt
View File

@ -5383,10 +5383,12 @@ bind /<path> [, ...] [param*]
listen on. If unset, all IPv4 addresses of the system will be listen on. If unset, all IPv4 addresses of the system will be
listened on. The same will apply for '*' or the system's listened on. The same will apply for '*' or the system's
special address "0.0.0.0". The IPv6 equivalent is '::'. Note special address "0.0.0.0". The IPv6 equivalent is '::'. Note
that if you bind a frontend to multiple UDP addresses you have that for UDP, specific OS features are required when binding
no guarantee about the address which will be used to respond. on multiple addresses to ensure the correct network interface
This is why "0.0.0.0" addresses and lists of comma-separated and source address will be used on response. In other way,
IP addresses have been forbidden to bind QUIC addresses. for QUIC listeners only bind on multiple addresses if running
with a modern enough systems.
Optionally, an address family prefix may be used before the Optionally, an address family prefix may be used before the
address to force the family regardless of the address format, address to force the family regardless of the address format,
which can be useful to specify a path to a unix socket with which can be useful to specify a path to a unix socket with