Project

General

Profile

Actions

Bug #2428

closed

Removing a limiter breaks any references to limiters after it

Added by Jim Pingle almost 12 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Traffic Shaper (ALTQ)
Target version:
Start date:
05/11/2012
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.x
Affected Architecture:
All

Description

It appears that the limiters are referenced only by their index in the current list of limiters, instead of by name or a stored index number, so this leads to problems when deleting limiters when others are in use, even if the ones being deleted are not in use.

Showing this one by example. Say you have 6 limiters:
  • aIN
  • aOUT
  • bIN
  • bOUT
  • cIN
  • cOUT
You have firewall rules that references:
  • bIN, bOUT - Limit "B" traffic
  • cIN, cOUT - Limit "C" traffic

Then you delete limiters aIN and aOUT since you decide you don't want them any more.

Suddenly, your rules have changed, you now have:
  • cIN, cOUT - Limit "B" traffic
  • none, none - Limit "C" traffic

The indexes for the limiters shifted down, since the earlier limiters were removed, so references by index are now invalid.

Actions

Also available in: Atom PDF