Hi,
Afaik, haproxy does not and did not reload on a wan-ip change on either
pfSense version.
There are a few options though.
-make haproxy frontend listen on 'any'
-or use a portforward to forward incoming traffic to 127.0.0.1 , haproxy
could then be listening on localhost:80.
Regards,
PiBa-NL
Op 2-5-2016 om 15:55 schreef Dominique Kaspar:
Hi,
we have a strange problem on our PFSense since we migrated to 2.3. We use the
HAProxy package to enable external access to several of our webservices
(webmail, taiga, wiki, kimai, owncloud) running on VMs in our LAN. In order to
do that, we have configured several frontends as well as several backends, and
all is working well - until the daily reset of the WAN IP happens (we get a
dynamic IP from out provider): then, HAProxy just fails to do its job until we
manually reload the service.
It seems to me that PFSense 2.3 has changed the way it reloads the haproxy
service after the WAN IP changes. Since this behavior is new to 2.3 (in 2.2.6,
this worked out-of-the-box), I am fairly sure there is a configuration out
there that can deal with this specific problem, but I can't seem to find it.
Can someone point me in the correct direction?
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
