Hi there i have just hit some strange behaviour or a bug on VRPP (beta3 and 4.10).I have two RB1000 two int for internet two for internal lan, i have setup a vrrp as it should be no FW no nothing just vrrp configured!!! For some reason when i setup my own Priority like R1 be 1 and R2 be 1 things are working as they should be:
But if i set higher PR on R1 and lower on R2 things are getting ugly:
But if i set higher PR on R2 and lower PR on R1 things are working again !!!Strange uhh!

For some reason VRRP like R2 much more of R1 dont know why would be nice if someone tell me , they all the same except Ip addresses and MACs.

Any comment from MikroTik stuff will be much appreciated!?

God speed

What should we see in the screenshots?

On first two i have two vrrp's vrrp1 and vrrp2 with same PR and as you can see there is RM flag and B flag and the failover is working.

On the second same configuration except i have set different PR on vrrp 1 an vrrp2 and all the ports are in RM flags and the failover not working.

Hello, I am running into this very same behvior. I have two routers with vrrp, everything goes according to plan but when I test the vrrp (I unplug cables and then plug them back in) all hell breaks loose!, both routers go to RM and nothing works. I am running ver 4.13 on a x86 platform.
Help...

Are there any updates on this issue? Is this a confirmed bug? I just want to know so I can make other arrangements instead of using VRRP. Also could this be caused by a bad config (Have you setup the routers from scratch or set one up and copied the config to the second one?)

From a scratch i haven't got any answers from Mikrotik about this issues and it shows more like a bug to me.

I have THE SAME ISSUE running RouterOS x86 v.5.2 L4 on 2 real PCs!

The strange is:

on LAN VRRP:
R1 priority 100 VRID 1 realIP 192.168.1.26/24
R2 priority 254 VRID 1 realIP 192.168.1.27/24
VRRPIP 192.168.1.5/32
Everything is OK. R2 is RM (cuz of higher priority) and R1 is B

on WAN VRRP:
R1 priority 100 VRID 2 realIP XXX.XXX.XXX.XX7/29
R2 priority 254 VRID 2 realIP XXX.XXX.XXX.XX8/29
VRRPIP XXX.XXX.XXX.XX4/32 (or /29 - nothing changes)
Both of VRRP is on RM state!

If both routers are Masters it meas that they are unable to communicate with each other. VRRP uses multicast to communicate with other VRRP routers.

If both routers are Masters it meas that they are unable to communicate with each other. VRRP uses multicast to communicate with other VRRP routers.

Of course i know that.
Everything i do, i do after consulting wiki.mikrotik.com

no firewall, no limitation between wan ports. RB250GS as switch with default conf and swos1.4
i'll explain more clearly:
When i disconnect r2 (master -pri.254), r1 becomes RM.
okay, i connect r2 back, it becomes RM and r1 becomes B.
okay! i just wait a few seconds and r1 becomes RM like r2

in the log there are "master down timer" appears.

what can i do?

no firewall, no limitation between wan ports. RB250GS as switch with default conf and swos1.4
i'll explain more clearly:
When i disconnect r2 (master -pri.254), r1 becomes RM.
okay, i connect r2 back, it becomes RM and r1 becomes B.
okay! i just wait a few seconds and r1 becomes RM like r2

in the log there are "master down timer" appears.

what can i do?

Hitting exactly the same things here. Two RB1100s, 5.2. Cisco switch, standard interface configs.

Working fine for me on 5.4 on two x86 connected via a 4507. The VRRP instances are running on VLAN subinterfaces. I remove the VLAN from the trunk to the master router (priority 254), the backup router (priority 1) becomes the master. I add the VLAN back in on the trunk to the master router and wait for spanning tree to converge and the backup router goes back to being a backup because it heard a higher priority, and stays a backup.

VRRP is working properly now.

You / I must really check that no firewall rule blocks the vrrp traffic. Check the NAT rules too !! you should exempt vrrp traffic from it.

And make sure the switch isn't being smart about your vrrp multicast traffic.

So, no bug here... just a user...

VRRP is working properly now.

You / I must really check that no firewall rule blocks the vrrp traffic. Check the NAT rules too !! you should exempt vrrp traffic from it.

And make sure the switch isn't being smart about your vrrp multicast traffic.

So, no bug here... just a user...

Hi thanks for the update!

Which version are you using?

I haven't got the time to test it on the new ones , and if you can confirm it's working it will be great!

P.S. i have used a dum switch between the two routers, just clear config with only vrrp set up!

It's been working fine for me on 4.17 on RB1100s, and 5.4 as well as 5.6 on x86 devices.