Project

General

Profile

Actions

Bug #9333

closed

limiters still active when marked inactive

Added by David Burns about 5 years ago. Updated about 5 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Traffic Shaper (Limiters)
Target version:
-
Start date:
02/17/2019
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4_2
Affected Architecture:

Description

Summary
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).

Expected behaviour
Limiters set inactive should be inactive

Actual behaviour
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

Actions

Also available in: Atom PDF