limiters still active when marked inactive
Using limiters for network testing - it appears that modifying config of limiters so that they are inactive does not appear to remove them from active limiters (Diagnostics / Limiter Info).
Limiters set inactive should be inactive
Limiters set inactive are active
Steps to reproduce:
1. Firewall / Traffic Shaper / Limiters - click New Limiter (eg. I created one "Down25M" for downloads and another "Up5M" for uploads)
2. Save limiter(s)
3. Apply changes
4. Diagnostics / Limiter Info - verify limiter config
5. Firewall / Traffic Shaper / Limiters - select Limiter & uncheck Enable box
6. Save limiter
7. Apply changes
8. Diagnostics / Limiter Info - observe limiter marked inactive is still showing as active
Workaround 1: Disable applicable firewall rules (using in/out pipe) to disable use of one or more limiter(s)
Workaround 2: Reboot if all limiters are no longer required. Given the processing overhead of dummynet limiters this seems to be only way of fully disabling limiters
#4 Updated by David Burns over 1 year ago
When any Limiter(s) is updated /tmp/rule.limiter is regenerated on Apply Changes.
Why doesn't a Diagnostics / States / Reset States flush existing limiters and reload the current /tmp/rule.limiter?
Alternatively if I delete a Limiter then it is deleted immediately from the Limiters (assuming it isn't referenced by a rule) ... Given this limiter deletion functionality exists why can't an inactive limiter be removed from table?