| Age | Commit message (Collapse) | Author |
|---|
|
Traffic-policy should be exist before than we can attach it
to an interface
The interface should exist before we can attach traffic-policy to it
(cherry picked from commit b8786cd1044b117e4629689efa7e632b0d47d271)
|
|
Fix every wrong default unit in rates for Limiter, Network Emulator, Rate Control,
Shaper and Shaper HFSC.
Delete default unit help for Random Detect.
|
|
(#446)
|
|
Signed-off-by: kouak <kouak@kouak.org>
|
|
Signed-off-by: kouak <kouak@kouak.org>
|
|
|
|
|
|
|
|
Priority queue automatically creates classes 1:[1-7] so we have to
use these as our classes.
Default class needs to be in the priomap (this is ugly, but it works
there must be a better way)
|
|
Bug 3643
Enhancement to expose kernel priority queuing.
|
|
|
|
Bug 7322
The match value is on port number and it can be either TCP or UDP.
|
|
Bug 6865
Port can be text or numeric value (like destination port).
|
|
|
|
This reverts commit bcb18b96605e194cf8c186467b0a4d853695f75e.
|
|
This adds:
traffic-policy myexample {
bandwidth 100Mbit
class 2 {
class 2a {
...
|
|
|
|
Queue limit is in packets not bytes.
(cherry picked from commit baaee833507361b891601101b4faa4c5baaa3c41)
|
|
Bug 5958
(cherry picked from commit 7f42350146525544bd38db2426d6f5c7b99302c2)
|
|
(cherry picked from commit ad3d4ae244558ee0377ef600ece482f22048ff03)
|
|
(cherry picked from commit 79a5811983069dbe5146cdd0db15ac28149d3af1)
|
|
(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.
|
|
For queue-type (other than fair-queue), it is allowable to have larger queue size.
Move validation into class checking.
|
|
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.
|
|
Bug 5849
|
|
Since queue limit of zero causes all packets to be dropped;
require user to configure a reasonable value
Bug 5842
|
|
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
|
|
The name ip exists in /etc/protocols as a pseudonym for all IP protocols.
But the Qos match logic doesn't support it so do not allow the user to
choose that value
Bug 5689
|
|
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.
|
