5d35e9c5e9
The bug is a listener only one, and only occured on FreeBSD. The FreeBSD issue has been reported here: https://forums.freebsd.org/threads/quic-http-3-with-haproxy.98443/ where QUIC traces could reveal that sendmsg() calls lead to EINVAL syscall errnos. Such a similar issue could be reproduced from a FreeBSD 14-2 VM with reg-tests/quic/retry.vtc as reg test. As noted by Olivier, this issue could be fixed within the VM binding the listener socket to INADDR_ANY. That said, the symptoms are not exactly the same as the one reporte by the user. What could be observed from such a VM is that if the first recvmsg() call returns the datagram destination address, and if the listener listening address is bound to a specific address, the calls to sendmsg() fail because of the IP_SENDSRCADDR ip option value set by cmsg_set_saddr(). According to the ip(4) freebsd manual such an IP options must be used if the listening socket is bound to a specific address. It is to be noted that into a VM the first call to recvmsg() of the first connection does not return the datagram destination address. This leads the first quic_conn to be initialized without ->local_addr value. This is this value which is used by IP_SENDSRCADDR ip option. In this case, the sendmsg() calls (without IP_SENDSRCADDR) never fail. The issue appears at the second condition. This patch replaces the conditions to use IP_SENDSRCADDR to a call to qc_may_use_saddr(). This latter also checks that the listener listening address is not INADDR_ANY to allow the use of the source address. It is generalized to all the OSes. Indeed, there is no reason to set the source address when the listener is bound to a specific address. Must be backported as far as 2.7. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.