On 2/12/13 7:32 AM, Cornelius Riemenschneider wrote:
The server is configured to listen to all traffic on eth1 to a specific port
(12340), so either traffic sent to its normal internal ip adress or to its VIP
address, in case keepalived assigned it to us will result in haproxy receiving
traffic on 12340.
I think that is the key issue - HAProxy will listen on all IPs assigned
to the interface when it is started. I do not believe it will bind to
new IPs as they are added by keepalived or some other clustering tool.