<![CDATA[VRRP expected MAC address behavior]]>What MAC addresses does TNSR intend to reply with to NDP/ARP requests? We've seen both the Virtual and Physical (of the current Master) on the wire (tcpdump/wireshark), but would expect more consistency.

It seems different clients throw different MACs in their neighbor cache, which drives lots of traffic blackholes, especially during failovers (even with gARP, or whatever it's called in v6 world).

TLDR: we haven't been able to successfully get VRRP reliably working between 2 routers even though Master/Backup states properly failover within timer periods. It appears to be driven by MAC address inconsistencies and/or internal memory structures on how VRRP is applied to an interface.

To elaborate on the "how TNSR applies VRRP to an interface scenario," we see strange traffic behavior when changing interface states between routers. This appears to mostly go away when we fully reboot the host and configuration is reprocessed (unacceptable) or we down/up the interface (not sustainable).

]]>https://forum.netgate.com/topic/196643/vrrp-expected-mac-address-behaviorRSS for NodeSat, 09 May 2026 23:59:23 GMTWed, 05 Mar 2025 19:55:10 GMT60<![CDATA[Reply to VRRP expected MAC address behavior on Tue, 24 Mar 2026 14:44:21 GMT]]>@gigabitguru What TNSR version do you run? This bugs were fixed on TNSR 23.11. Here is the details: https://docs.netgate.com/tnsr/en/latest/releases/release-notes-23.11.html#vrrp

]]>https://forum.netgate.com/post/1240173https://forum.netgate.com/post/1240173Tue, 24 Mar 2026 14:44:21 GMT