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

    Dhcp using carp, host has different traceroute path

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 1 Posters 378 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.
    • K
      kutsheax
      last edited by

      Hi All,

      I have a DHCP server using carp. SYNC works perfectly fine. HA is also as it is expected. The dhcp leases is also working without a hitch.

      The connection requirements is just an internal network without wan connectivity.

      here's the diagram:
      6855dddb-f5a8-4a4c-924c-8739f1d9d5b3-image.png

      Master
      CARP 10.133.201.3
      tag0876 interface ip - 10.133.201.2
      DHCP range - 10.133.201.6 - 62
      DHCP gw- 10.133.201.3
      Failover peer ip - 10.133.201.4

      Backup
      CARP 10.133.201.3
      tag0876 interface ip - 10.133.201.4
      DHCP range - 10.133.201.6 - 62
      DHCP gw- 10.133.201.3
      Failover peer ip - 10.133.201.2

      10.133.201.1 - its the core switch interface vlan ip - Next hop

      I have enable the Manual NAT outbound where outbound NAT is disabled.

      Here's the problem on the host. when i traceroute the target destination. there are several path appearing on the source host(dhcp host)

      Here are my sample:
      1st server - 10.133.201.9

      58642c52-5879-4cc4-9a1d-08f6c211a8a7-image.png

      as you can see. traffic passes through the x.x.201.2 and to the x.x.201.1 routes

      3f30a25c-544b-4411-8237-227647424a57-image.png

      Successful telnet is good on this one.

      on the second server - 10.133.201.48
      320de3cb-e342-463e-8637-6f2a22b52ee7-image.png

      as you can see the traceroute on server 2 is only passing on the x.x.201.1 neglecting the x.x.201.2. and because of this, the telnet fails below.

      ad00cd16-896e-41e3-8f69-9dd11ff47e30-image.png

      The dhcp host got me confused why it behaves differently when in fact they have the same dhcp/dns setup. Appreciate the help you can provide.

      K 1 Reply Last reply Reply Quote 0
      • K
        kutsheax @kutsheax
        last edited by kutsheax

        @kutsheax

        i got this solve by shutting down the hosts and removing the lease. Everything works fine after starting the problematic hosts. WOL is the culprit as i accidentally enabled on certain mac addresses. The problem with the WOL status is it does not even shows up on the dhcp leases.

        K 1 Reply Last reply Reply Quote 0
        • K
          kutsheax @kutsheax
          last edited by

          I have another issue, when i clone another server, same problem arise as above. the worst thing is, even if i delete the lease. the route does not pass on the interface ip which is x.x.201.2.

          here's the snippet from above, where interface ip x.x.201.2 is not even visible anymore. The others dhcp clients are complete by showing the x.x.201.2 on the traceroute.
          f68e9537-2d77-482a-babf-240a49f1cd88-image.png

          below is the correct one:
          875b21a1-ffa0-4bec-aa61-bf2c9d531e55-image.png

          so now, whatever i do, disable/enable NAT. nothing works!

          does anybody experience same as mine? or is this a bug???

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