Keepalived/Vrrp with Shorewall

[Dominik Klein]

> You want only my keepalived.conf ?

Well I could not find anything that would have confirmed my suggestion.

Anything like

"block { config value }" in one line caused weird errors in my tests 
with keepalived so I just wanted to make sure.

Does this "ping-pong" situation end after those 8 mentioned steps or 
does it continue?
Do you see the appropriate vrrp packets on the specified interface on 
master and slave?

I'd suggest reducing your config to one VIP, add appropriate values for 
broadcast and interface to the virtual_ipaddress block (see example 
below 1),disable shorewall to make sure it is not the problem and then 
look for packets with tcpdump (see below 2)

1
virtual_ipaddress {
         10.2.20.20/24 brd 10.2.20.255 dev eth0
     }

2
tcpdump -i eth net 224.0.0.0/8

You should be able to see the virtual router id and the priority for 
each packet so you can see which machine sees which packets on which 
interface.