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

    Limiters - Possible Bug +24.11-RELEASE

    Scheduled Pinned Locked Moved Traffic Shaping
    8 Posts 3 Posters 1.3k 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.
    • provelsP
      provels
      last edited by provels

      Hello. I was working with limiters today and found whenever I changed a parameter and tried to save, I got a message saying the limiter and child queue were the same name (which, as you can see, they are not). I was able to change the limiter name, save, make the edit, save, then rename the limiter to the old name. Possibly just me, and if so, there is a workaround.
      Thanks for reading!

      46dce2bf-07c9-4017-9090-76f5d5ad3eae-image.png

      Peder

      MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
      BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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

        @provels "We" encountered it too. You can not save a child twice, at least not without changing its name every time.

        1 Reply Last reply Reply Quote 1
        • dennypageD
          dennypage
          last edited by

          Have you updated System Patches? There are three fixes for input Validation errors in there, and your's sounds like the first one.

          https://redmine.pfsense.org/issues/13158
          https://redmine.pfsense.org/issues/13687
          https://redmine.pfsense.org/issues/15914

          provelsP 1 Reply Last reply Reply Quote 0
          • provelsP
            provels @dennypage
            last edited by provels

            @dennypage Yes, I've applied all the latest patches. The error in the first bug I see occasionally, but not consistently. When I see it, I "think" I have been hitting the delete button to ack. The naming error I can reproduce consistently. If I make a parameter change, I have to rename the limiter at the same time and save. I can then rename the limiter back to it desired name.

            EDIT - I just saw JimP put out a new patch today, now installed.
            EDIT2 - No difference.

            Peder

            MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
            BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

            dennypageD 1 Reply Last reply Reply Quote 0
            • dennypageD
              dennypage @provels
              last edited by

              @provels said in Limiters - Possible Bug +24.11-RELEASE:

              The naming error I can reproduce consistently. If I make a parameter change, I have to rename the limiter at the same time and save. I can then rename the limiter back to it desired name.

              Have you created a Redmine?

              provelsP 1 Reply Last reply Reply Quote 0
              • provelsP
                provels @dennypage
                last edited by

                @dennypage Yup, https://redmine.pfsense.org/issues/15990

                Peder

                MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

                dennypageD 1 Reply Last reply Reply Quote 1
                • dennypageD
                  dennypage @provels
                  last edited by

                  @provels And just like that, a fix is available. Surprised to see it was a result of one of the prior patches 😊

                  1 Reply Last reply Reply Quote 0
                  • provelsP
                    provels
                    last edited by

                    Working fine!

                    Peder

                    MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
                    BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

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