Age | Commit message (Collapse) | Author |
|
(cherry picked from commit 2c9b0e0641b24dc79320282eff358079b3c7c7c3)
|
|
This reverts commit cf51e90bfc2d1c3b58192a726e786b598681fb71.
Conflicts:
templates/traffic-policy/limiter/node.tag/class/node.tag/precedence/node.def
|
|
Priority for default rule makes no sense. The default is always
after all other rules.
|
|
Add spaces and use u32: format
|
|
This allows use of IANA (/etc/services) values for port names:
example:
traffic-policy shaper SS {
class 2 {
match SMTP ip destination port smtp
}
}
|
|
Replace all usage in this package of comp_help with new val_help
|
|
And fix some typos
|
|
Allow using common values supported by TC filter.
|
|
There is no way for firewall mark to be useful in limiter policy
since limiter is only allowed on ingress. And ingress takes place
before firewall rules are applied.
|
|
Bug 5407
This fixes the confusing usage of priority field in both shaper
and limiter class. In limiter, it is renamed to precedence since
it controls the order of match rule evaluation.
|
|
Bug 5799 - Add matching on firewall mark values
Bug 5795 - Block match rules that have multiple underlying filters
|
|
Bug 5783
|
|
This adds:
set traffic-policy limiter TL default bandwidth 1mbit
|
|
Current (Kenwood and earlier):
set qos-policy traffic-shaper TS { ...classes }
set qos-policy traffic-limiter TL { ...classes }
seq qos-policy network-emulator NE ...
set qos-policy random-detect RD ...
set qos-policy rate-limiter RC ...
set qos-policy round-robin RR ...
set interfaces ethernet eth0 qos-policy out TS
set interfaces ethernet eth0 qos-policy in TL
New (Larkspur and later):
set traffic-policy shaper TS { ...classes }
set traffic-policy limiter TL { ...classes }
seq traffic-policy network-emulator NE ...
set traffic-policy random-detect RD ...
set traffic-policy rate-control RC ...
set traffic-policy round-robin RR ...
set interfaces ethernet eth0 traffic-policy out TS
set interfaces ethernet eth0 traffic-policy in TL
set interfaces ethernet eth0 redirect ifb0
set interfaces ethernet eth0 mirror eth2
Note:
1. Only one of the following is allowed: "redirect", or "mirror"
2. Traffic-policy limiter is allowed with redirection/mirror and takes place
before mirror/redirect action (NEW)
3. Limiter policy may applied on output (NEW)
4. Only limiter policies can be applied on input (same as previous releases)
This does add some new functionality (#2, and #3) which are possible because
of how filter classes are implemented.
|