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

    Limiter on WAN rule

    Scheduled Pinned Locked Moved Traffic Shaping
    4 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.
    • F
      falcor
      last edited by

      Hey!

      I have a WAN rule that is part of a NAT redirect.  The rule basically allows TCP 7001 to an internal IP address.  I have someone using it to access some files, but at the same rate I don't want them saturating my upstream pipe (it's not that big.) So I created two limiters at 500Kb each and applied them in each direction for the rule.  But when I do this the rule allowing access via that NAT is then not followed by PfSense.  If I remove the rate limiters from the rule (e.g. setting it to none) then the rule works again.

      Why I do the same thing to a rule on the LAN, it seems to work just fine.

      Did I miss something and Limiters are not allowed on WAN interfaces or could I possibly have done something wrong?  Normally I just apply a limited to a firewall rule and then it applies to that rule and uses the limiter as a queue depending on how it is masked in the limiter setup.  Right now it is set to 0.0.0.0 which should be anything.  Thanks!

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

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

        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
        • F
          falcor
          last edited by

          thanks!  Seems like this has been going on for a while too.  Sad.

          I found the same issue could be replicated if I setup an in/out queue for the interface.  As soon as it filled no new traffic was passed from the WAN to the LAN.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            FYI- This is no longer a problem on 2.4.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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