mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-19 02:29:31 -05:00
HAProxy - Load balancer
2d380926ba
When receiving a QUIC datagram, destination address is retrieved via recvmsg() and stored in quic-conn as qc.local_addr. This address is then reused when using the quic-conn owned socket. When listener socket mode is preferred, send operation did not specify the source address of the emitted datagram. If listener socket is bound on a wildcard address, the kernel is free to choose any address assigned to the local machine. This may be different from the address selected by the client on its first datagram which will prevent the client to emit next replies. To address this, this patch fixes the UDP source address via sendmsg(). This process is similar to the reception and relies on ancillary message, so the socket is left untouched after the operation. This is heavily platform specific and may not be supported by some kernels. This change has only an impact if listener socket only is used for QUIC communications. This is the default behavior for 2.7 branch but not anymore on 2.8. Use tune.quic.socket-owner set to listener to ensure set it. This should be backported up to 2.7. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)