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

    Limiter error

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    35 Posts 6 Posters 9.7k 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
      eri--
      last edited by

      The first in line wins, that is the behaviour.

      1 Reply Last reply Reply Quote 0
      • X
        xbipin
        last edited by

        one problme i noticed that when a schedule expires the config file ends up like this and that client looses complete internet access

        
        pipe 5 config 
        

        isnt it better to skip the whole line only so his connectivity doesnt break

        1 Reply Last reply Reply Quote 0
        • X
          xbipin
          last edited by

          also noticed with 6th nov snap that if u have a limiter and schedule set to none then it results in this config and doesnt limit anything

          pipe 5 config  bw 120Kb bw 0
          
          1 Reply Last reply Reply Quote 0
          • E
            eri--
            last edited by

            Should be fixed on next snapshot.

            Thank you for reporting it.

            1 Reply Last reply Reply Quote 0
            • X
              xbipin
              last edited by

              @ermal:

              Should be fixed on next snapshot.

              Thank you for reporting it.

              tried the snap after the patch but still same, config shows as below and limiter doesnt limit with schedule set as none

              pipe 5 config  bw 120Kb bw 0
              
              pipe 6 config  bw 400Kb bw 0
              
              1 Reply Last reply Reply Quote 0
              • E
                eri--
                last edited by

                You really should have a strange config.xml there.
                I pushed another tuning to the code so test that out.

                1 Reply Last reply Reply Quote 0
                • B
                  bardelot
                  last edited by

                  @ermal: There is no '$found = true;' before breaking out of the foreach loop, leading to the additional 'bw 0'.

                  1 Reply Last reply Reply Quote 0
                  • X
                    xbipin
                    last edited by

                    config seems all fine

                    	 <dnshaper><queue><name>ashishup</name>
                    			<number>5</number>
                    			 <qlimit><plr><description><bandwidth><bw>120</bw>
                    					<bwscale>Kb</bwscale>
                    					<bwsched>none</bwsched></bandwidth> 
                    			<bandwidthtype>Kb</bandwidthtype>
                    			<enabled>on</enabled>
                    			 <buckets><mask>none</mask>
                    			<delay>0</delay></buckets></description></plr></qlimit></queue> 
                    		 <queue><name>ashishdown</name>
                    			<number>6</number>
                    			 <qlimit><plr><description><bandwidth><bw>400</bw>
                    					<bwscale>Kb</bwscale>
                    					<bwsched>none</bwsched></bandwidth> 
                    			<bandwidthtype>Kb</bandwidthtype>
                    			<enabled>on</enabled>
                    			 <buckets><mask>none</mask>
                    			<delay>0</delay></buckets></description></plr></qlimit></queue></dnshaper> 
                    
                    1 Reply Last reply Reply Quote 0
                    • X
                      xbipin
                      last edited by

                      even after the latest patch, the situation is same

                      1 Reply Last reply Reply Quote 0
                      • E
                        eri--
                        last edited by

                        Oh found the issue.
                        Thank you xbipin for the persistence.

                        1 Reply Last reply Reply Quote 0
                        • P
                          phil.davis
                          last edited by

                          I had just made the same change to fix my system and was about to submit it. The fix Ermal has just committed is exactly what I did, and it is working.
                          /tmp/rules.limiter on a test system:
                          Before:

                          
                          pipe 1 config  bw 64Kb bw 0 mask src-ip 0xffffffff
                          
                          pipe 3 config  bw 16Kb bw 0
                          
                          pipe 4 config  bw 16Kb bw 0
                          
                          

                          After:

                          
                          pipe 1 config  bw 64Kb mask src-ip 0xffffffff
                          
                          pipe 3 config  bw 16Kb
                          
                          pipe 4 config  bw 16Kb
                          
                          

                          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                          1 Reply Last reply Reply Quote 0
                          • X
                            xbipin
                            last edited by

                            works fine now, thanks ermal

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