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

    Traceroute not working on linux

    General pfSense Questions
    4
    6
    523
    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.
    • S
      strangegopher
      last edited by

      traceroute does not work. the output is like this:

      traceroute to google.com (209.85.231.104), 30 hops max, 52 byte packets
      1  * * *
      2  * * *
      3  * * *
      4  * * *
      
      

      Any idea why? It was working fine few days ago but now does not work.
      I am able to traceroute directly on pfsense but I can't do traceroute from my laptop to any device inside or outside my network.

      edit: traceroute with tcp (-T) and icmp (-I) works but only gives one hop. but traceroute with udp (-U)/default does not work.
      edit2: I disabled firewall on my laptop with no success.

      1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott
        last edited by

        It works for me.  I'm running openSUSE 42.3.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          Works with a Lubuntu client.

          1 Reply Last reply Reply Quote 0
          • GruensFroeschliG
            GruensFroeschli
            last edited by

            You don't happen to do something strange and created a rule which blocks ICMP?

            We do what we must, because we can.

            Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

            1 Reply Last reply Reply Quote 0
            • S
              strangegopher
              last edited by

              @GruensFroeschli:

              You don't happen to do something strange and created a rule which blocks ICMP?

              Not really.

              It seems like issue with my laptop itself. I ran a kali virtual machine in bridge mode and did traceroute after restarting my router and switch and this is the output I got:

              traceroute pfsense.org
              traceroute to pfsense.org (208.123.73.69), 30 hops max, 60 byte packets
               1  router.localdomain (10.10.100.1)  1.530 ms  1.554 ms  1.352 ms
               2  www.pfsense.org (208.123.73.69)  10.761 ms  11.280 ms  11.200 ms
               3  www.pfsense.org (208.123.73.69)  12.107 ms  13.464 ms  13.210 ms
               4  www.pfsense.org (208.123.73.69)  11.823 ms  11.853 ms  11.947 ms
               5  www.pfsense.org (208.123.73.69)  16.103 ms  15.877 ms  15.292 ms
               6  www.pfsense.org (208.123.73.69)  15.234 ms  23.681 ms  23.065 ms
               7  www.pfsense.org (208.123.73.69)  15.443 ms  13.555 ms  14.085 ms
               8  www.pfsense.org (208.123.73.69)  15.090 ms  14.616 ms  14.334 ms
               9  www.pfsense.org (208.123.73.69)  68.960 ms  69.847 ms  69.734 ms
              10  www.pfsense.org (208.123.73.69)  68.540 ms  68.651 ms  68.225 ms
              11  www.pfsense.org (208.123.73.69)  69.721 ms  69.580 ms  69.706 ms
              12  www.pfsense.org (208.123.73.69)  70.258 ms  70.256 ms  70.179 ms
              13  www.pfsense.org (208.123.73.69)  71.356 ms  70.911 ms  70.650 ms
              14  www.pfsense.org (208.123.73.69)  108.362 ms  68.683 ms  69.740 ms
              15  www.pfsense.org (208.123.73.69)  74.016 ms  74.125 ms  73.893 ms
              16  www.pfsense.org (208.123.73.69)  74.712 ms  74.664 ms  74.575 ms
              17  www.pfsense.org (208.123.73.69)  74.558 ms  75.646 ms  75.351 ms
              18  www.pfsense.org (208.123.73.69)  74.534 ms  74.582 ms  74.567 ms
              19  www.pfsense.org (208.123.73.69)  75.680 ms  74.804 ms  75.559 ms
              

              Not sure why its only giving me one ip address. But local ip address traceroute does not work at all.
              I get proper output when I do traceroute on pfsense itself.

              1 Reply Last reply Reply Quote 0
              • S
                strangegopher
                last edited by

                Found the issue. It was fq_codel.

                https://forum.pfsense.org/index.php?topic=126637.msg765566;topicseen#msg765566

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