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

    Traceroute going via Secondary instead of Primary in HA cluster

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    2 Posts 1 Posters 300 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.
    • N
      nfern
      last edited by

      I have 2 netgate routers - master 10.x.x.196 and secondary 10.x.x.197- CARP IP configured is 10.x.x.189. CARP status shows correctly.
      When i traceroute from from my servers, which go via pfsense to my clients, i notice that traffic goes via 10.x.x.197 instead of 10.x.x.196

      Tracing route to xxxxxxxxxxxx.local [10.x.x.157]
      over a maximum of 30 hops:

      1 <1 ms <1 ms <1 ms 10.x.x.197
      2 <1 ms <1 ms <1 ms xxxxxxxxxxxxxx.local [10.x.x.157]

      Trace complete.

      N 1 Reply Last reply Reply Quote 0
      • N
        nfern @nfern
        last edited by

        When i try to ping the other way around, it goes via the correct path via primary 10.x.x.196

        Tracing route to 10.x.x.41 over a maximum of 30 hops

        1 <1 ms <1 ms <1 ms 10.x.x.196
        2 <1 ms <1 ms <1 ms 10.x.x.41

        Trace complete.

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