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

    Bandwidth limiting not working in 2.2.5?

    Scheduled Pinned Locked Moved Traffic Shaping
    5 Posts 3 Posters 1.6k 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.
    • E Offline
      ElrondBCN
      last edited by

      I have a large number of pre-existing rules on my Firewall, and if I add the In/Out limiters to any of the WAN rules, the rule stops working and traffic doesn't pass properly. Any suggestions?

      1 Reply Last reply Reply Quote 0
      • DerelictD Offline
        Derelict LAYER 8 Netgate
        last edited by

        Use 2.1.5. Limiters are broken on 2.2.X.

        At least on anything that requires pf rdr, apparently, such as NAT.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • E Offline
          ElrondBCN
          last edited by

          Thx for the quick response. I was reading through the forums and saw that this is an open bug for over a year:

          https://redmine.pfsense.org/issues/4326

          I wonder when it will get addressed.

          1 Reply Last reply Reply Quote 0
          • C Offline
            cmb
            last edited by

            Use 2.1.5 is horrible advice. ALTQ queues can be used instead in circumstances where limiters won't work. There were a variety of situations with NAT where limiters didn't work right in 2.1.5 either.

            1 Reply Last reply Reply Quote 0
            • DerelictD Offline
              Derelict LAYER 8 Netgate
              last edited by

              Not in all cases such as a 3x3 Mbit pipe per IP address.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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