Bug #14258


HA-proxy, IPV6-address in combination with portnumber => fatal

Added by Louis B about 1 year ago. Updated about 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:


I am setting up HA-proxy using IPV4 and IPV6. When trying to define an IPV6 frontend, there is a prolbem

When e.g. creating (a top level) fronted for eg
<IPV6-x><porty> there is a fatal error.

As example take 'wan interface (ipv6)' as IP and port '123' you will have a fatal error.

What seems ++ to happen is that the gui frontend is handing over a wrong string to the HA-proxy engine
- 'wan interface (ipv6)':123 seems to be send to the backend like [<IPV6>:123] which is an invalid address
- what should be send is [<ipv6>]123

As a very doubtful work around I did enter ^<space>123>, which is excepted .... (however if it is OK !?)

I have been testing with latest 2.7 build, together with the 'normal HA-package'and the 'develop HA-package' versions. Both seems to have the problem
Note that
- I am trying to setup my config using the 'develop version', since that one is significant newer (and the 'normal' version does have the problem as well).
- I did remove the normal HA-proxy version AND wiped all HA-proxy related data with an editor from the config, before installing the devel-edition.
(when removing an package, you should IMHO have the option ++ to remove the package related data as well)

Below an example of the error shown

[NOTICE] (77459) : haproxy version is 2.7.6-4dadaaa
[NOTICE] (77459) : path to executable is /usr/local/sbin/haproxy
[ALERT] (77459) : config : parsing [/var/etc/haproxy_test/haproxy.cfg:91] : 'bind' : invalid address: 'fe80::6a05:caff:fe5a:813d%pppoe1' in 'fe80::6a05:caff:fe5a:813d%pppoe1:85'
[ALERT] (77459) : config : Error(s) found in configuration file : /var/etc/haproxy_test/haproxy.cfg
[ALERT] (77459) : config : Fatal errors found in configuration.


Actions #1

Updated by Jim Pingle about 1 year ago

  • Project changed from pfSense to pfSense Packages
  • Category changed from High Availability to haproxy
  • Release Notes deleted (Default)
Actions #2

Updated by Louis B about 1 year ago

Attached a picture from another situation where the IPV6-addresses are not properly extracted / handover from the GUI to the application.

Probably / perhaps as a consequence (I do not know) is this:
- if a frontend is listening to multiple ports, I am almost sure that the intention is that those portnumbers are forwarded to the backend and from the backend to the destination server (if the packend port is left empty).
- however since it is at the moment is, due to errors in the address-portnumber handling is impossible to leave the port number empty, I can not test.

Whats ever .. when developing, please test IPV6 as well


Also available in: Atom PDF