To listen on the same port for IPv6 and IPv4, use this:
bind :::80 v4v6Code language: CSS (css)
Admittedly, this was an intuitive guess that appears to have been correct… but rather than just post a “lucky” guess as the answer, even though it works, it seems like I should justify it.
the v4v6 keyword makes haproxy bind to a v4 socket only.
My first intuition was that it’s not
v4v6 but rather the use of
:80 (or, more precisely, the use of no IP address at all, just a port number) that causes this socket to listen on IPv4 only.
This seems to be confirmed in the docs for
addressis optional and can be a host name, an IPv4 address, an IPv6 address, or
'*'. It designates the address the frontend will listen on. If unset, all IPv4 addresses of the system will be-listened on. The same will apply for
'*'or the system’s special address “
0.0.0.0“. The IPv6 equivalent is ‘::’.
So the following three forms are all equivalent, and are all interpreted as being IPv4 by HAProxy:
bind :80 bind *:80 bind 0.0.0.0:80Code language: CSS (css)
Next, there is one sentence in the docs for
v4v6 could be read in isolation to indicate that
v4v6 might be usable to extend one of the above bind statements to listen on IPv6…
It is used to bind a socket to both IPv4 and IPv6 when it uses the default address.
…hmmm, but I suspect that this actually means “the v6 default address” (
Doing so is sometimes necessary on systems which bind to IPv6 only by default.
…and now, I suspect it even more…
It has no effect on non-IPv6 sockets, and is overridden by the
So, it appears that
v4v6 only modifies
bind directives that specify the IPv6 default listen address, which is
:: (the 3rd
: is the separator between the address and the port), and is ignored for others.