Actions
Bug #3924
closedRenaming limiters removes them from firewall rules
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Traffic Shaper (Limiters)
Target version:
Start date:
10/10/2014
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
Description
Hello,
- Created two bandwidth limiters "OutLimit" and "InLimit".
- Selected then as In/Out in a firewall WAN rule
- Went to shaper and renamed the limiters to "LimitOut" and "LimitIn"
- Went to firewall WAN rule - limiters are not selected, shows None/None.
Suggestion: renaming limiters should not remove them from firewall rules where they are used.
I didn't test with other traffic shaper item types, same issue could be there as well.
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Confirmed
- Affected Version changed from 2.1.x to All
- Affected Architecture added
- Affected Architecture deleted (
amd64)
Updated by Chris Buechler almost 10 years ago
- Category changed from Traffic Shaper (ALTQ) to Traffic Shaper (Limiters)
Updated by Viktor Gurov over 4 years ago
Updated by Steve Russell over 4 years ago
Thanks! I just did that to myself multiple times yesterday!
Updated by Jim Pingle over 4 years ago
- Status changed from Confirmed to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Anonymous almost 4 years ago
- Status changed from Feedback to Resolved
Actions