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

    Trace route repeating same hop

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 2 Posters 1.8k 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.
    • C
      capone
      last edited by

      Not sure what I broke... so, was looking for alittle help... when I do a trace route (windows or linux) I get my router as the 1st hop...but then the rest of the hops are all the same:

      2119e35b-47ec-4ef6-8042-fe99c55e9705-image.png

      Any ideas?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by stephenw10

        Routing loop probably. You added a default route via something that isn't the WAN?

        If you have multiple gateways on that system make sure the WAN is set as the default v4 gateway in System > Routing > Gateways. If it's set to auto it may have chosen another gateway if the WAN went down.

        Except the it appears to be looping at the Google end. Not much you can do about that if so.

        Steve

        C 1 Reply Last reply Reply Quote 0
        • C
          capone @stephenw10
          last edited by capone

          @stephenw10

          That's actually the one spot I did check... And the IPV4 DEFAULT gateway is the WAN.

          Ipv6 works correctly, btw.

          Also really doesn't matter what I do a traceroute to... The pattern is the same.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            You just get loops all showing the target IP? How exactly are you running traceroute?

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Ah, are you running outbound limiters for FQ-CoDel?

              https://forum.netgate.com/topic/142522/fq_codel-qos-breaks-traceroute

              C 1 Reply Last reply Reply Quote 0
              • C
                capone @stephenw10
                last edited by

                @stephenw10

                YESSSSSSSS! That's it... I did setup the outbound limiters for FQ-CoDel!

                Is this a side effect? bug? normal behaviour? Correctable?

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  It's a side effect I guess you could best call it. You need to add the two floating firewall rules shown here to bypass the limiters for traceroute and ping:
                  https://forum.netgate.com/post/807490

                  Steve

                  C 1 Reply Last reply Reply Quote 0
                  • C
                    capone @stephenw10
                    last edited by

                    @stephenw10 Thank you! :-) I haven't tried the step just yet... family time. I'll get to it over the next couple of days.

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