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

    Bufferbloat guide causes NAT bug

    Scheduled Pinned Locked Moved Traffic Shaping
    6 Posts 3 Posters 1.0k 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.
    • F
      fused
      last edited by

      https://docs.netgate.com/pfsense/en/latest/recipes/codel-limiters.html

      I used this guide to reduce bufferbloat and it works just fine. However, I noticed that when I perform a traceroute on any of my clients, I will see the destination IP address on every single hop. As soon as I disable the Traffic Limiter queues, traceroute works properly and shows the correct IP address on every hop.

      Example:

      bufferbloat_tracert.PNG

      Anyone else run into this problem? I'm running 22.01-RELEASE on a Netgate 3100.

      Bob.DigB 1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @fused
        last edited by Bob.Dig

        @fused said in Bufferbloat guide causes NAT bug:

        Anyone else run into this problem?

        No. Next time show your command too.

        F 1 Reply Last reply Reply Quote 0
        • F
          fused @Bob.Dig
          last edited by fused

          @bob-dig all I typed was tracert 1.1.1.1 in command prompt but I get your point. This happens on all client types: smartphones, linux, windows, etc.

          Here are the results from the router itself:

          SOURCE: LAN INTERFACE
          CODEL LIMITERS: ENABLED
          router_traceroute_lan_int.PNG

          SOURCE: LAN INTERFACE
          CODEL LIMITERS: DISABLED
          router_traceroute_lan_int_queues_disabled.PNG

          SOURCE: WAN INTERFACE
          CODEL LIMITERS: ENABLED
          router_traceroute_wan_int.PNG

          Bob.DigB 1 Reply Last reply Reply Quote 0
          • Bob.DigB
            Bob.Dig LAYER 8 @fused
            last edited by

            @fused Next is to show your actual rule you made.

            1 Reply Last reply Reply Quote 0
            • T
              tman222
              last edited by

              Hi @fused -

              This is actually a known issue that has been worked on:

              https://redmine.pfsense.org/issues/9263
              https://docs.netgate.com/pfsense/en/latest/releases/22-05.html#traffic-shaper-limiters

              It should be working better in pfSense 22.05 once it's released. I recently upgraded one my 22.01 systems to the 22.05 Beta version (22.05-RC) and can confirm that the traceroutes do work properly for me now.

              Hope this helps.

              F 1 Reply Last reply Reply Quote 0
              • F
                fused @tman222
                last edited by

                @tman222 awesome! thanks for the information :)

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