Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    VRRP expected MAC address behavior

    Scheduled Pinned Locked Moved TNSR
    1 Posts 1 Posters 255 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gigabitguruG
      gigabitguru
      last edited by gigabitguru

      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).

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.