# Using Keepalived (VRRP) for source IP failover

**URL:** <https://discourse.haproxy.org/t/using-keepalived-vrrp-for-source-ip-failover/2478>\
**Category:** Help!\
**Created:** [May 10, 2018, 12:00am UTC](https://discourse.haproxy.org/t/using-keepalived-vrrp-for-source-ip-failover/2478 "2018-05-10T00:00:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakinov](https://avatars.discourse-cdn.com/v4/letter/j/4491bb/32.png) [@jakinov](https://discourse.haproxy.org/u/jakinov)\
**Post date:** [May 10, 2018, 12:00am UTC](https://discourse.haproxy.org/t/using-keepalived-vrrp-for-source-ip-failover/2478/1 "2018-05-10T00:00:57Z")

</div>

In my case, I need my HAProxy to use a specific source IP when connecting to any of the back-end servers. I’m currently using keepalived for automatic failover and switching over an IP from BACKUP to MASTER. If I don’t have an IP binded to the backup, then the backup will basically log a whole bunch complaining it can’t use the IP that’s supposed to be dynamically binded to it.

Is there a way I can configure it so HAProxy doens’t complain? Is it bad practice to leave HAProxy running with an IP it can’t use? I’m just wondering if there’s a better/cleaner way to achieve what I want that won’t spam my server with error logs.

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [May 10, 2018, 9:55am UTC](https://discourse.haproxy.org/t/using-keepalived-vrrp-for-source-ip-failover/2478/2 "2018-05-10T09:55:03Z")

</div>

To bind to a non-existant IP on your frontend, use the [transparent](http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#5.1-transparent) bind keyword.

I’m not sure what this has to do with the source IP haproxy uses to connect to your backend: that is supposed to be the actual, physical IP address configured on the haproxy server, not the failover IP.