#10 Setting of default route broken in keepalived 1.2.8 and 1.2.9

[Torsten]

Hi,

I've been using keepalived 1.2.7 successfully for over a year now to implement VRRP on our primary and backup firewalls.

My setup therefore includes sections like:

virtual_routes {
    default via 1.2.3.4 dev vrrp_extern_0
}

After upgrading to keepalived 1.2.8 and, subsequently, to 1.2.9, these route definitions stopped working, with keepalived complaining about "default" not being a valid IP-address.

I replaced the word 'default' by 0.0.0.0/0 only to realize that there seems to be a bug in prefix handling, too. In fact, according to /proc/net/route, the route set by keepalived was 0.0.0.0/32, thus being a blackhole instead of a default route definition.

I was able to circumvent the problem by setting up notify_master and notify_backup scripts that set and remove the necessary route entries by invoking the 'ip route' command. However, I consider the above behavior as being a serious bug that needs to be fixed.

Best,
Torsten