Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Random detect requires bandwidth which is not part of round robin
policy. Therefore drop it as a configurable value.
Bug 4595
(cherry picked from commit b1b823012b2a1aa0fa8578054fc1179f92a32c2f)
|
|
Bug 4590
(cherry picked from commit 447b5430e8f4019e5d3b6e3f1f2025712d1c7b7f)
|
|
The $VAR(.) is not set on end node, so have to go hunting
for policy type.
Related to Bug 4545
(cherry picked from commit 39712bfaf390a4435218a14308cc6efa1a2d39b8)
|
|
The CLI end: node does work correctly, so don't need to go walking configuration
manually
Bug 4545
(cherry picked from commit 377896b296827e4d7c3c20debb3487605c45bbe3)
|
|
Two more (optional) parameters for random detect precedence groups.
Bug 4518,4519
(cherry picked from commit 8104da09f5da338c6ce0813c367262de4e417598)
|
|
Bug 4516
(cherry picked from commit 26890ac98e3ed6c0830e61fa91f306fea0cc227a)
|
|
CLI quoting in expressions seems to have changed, so adapt.
Bug 4485
|
|
Bug 4485
Change template to deal with CLI changes in quoting evaluation
of expressions.
|
|
|
|
Packet reordering doesn't work unless there are packets in the queue,
and no packets are held unless there is a delay.
|
|
The RED queue setup needs a rate value and RR doesn't have rate configuration.
|
|
Make a simpler version of WRED that acts more like Cisco.
Use Diffserv on Linux paper for example of how to use DSMARK and GRED
to achieve similar result.
|
|
GRED only allows 1..16 for classes, and reserve one for default
so only 1..15 are ok for class value.
|
|
Class value of 2 is allowed.
|
|
|
|
Having too long a name messes up column output on operational commands.
|
|
Bug 4296
Ehancement to allow configuring GRED as form of weighted RED.
|
|
Use existing u32 infrastructure to match in header
|
|
It needs more work (not ready for prime time).
|
|
|
|
New policy allowing strict priority traffic assignment
|
|
Round-robin class based policy
|
|
|
|
Bug 4230
Allow matching based on IPV6 addresses and ports
Generalize existing matching code.
|
|
|
|
Don't break new config process
|
|
Makes code simpler and will work better with config system.
Also eliminates need for isChanged() code.
|
|
Eliminate need for begin, just check for name conflicts at create.
|
|
New QoS feature to allow emulating WAN characteristics
|
|
There are two ways to input rate limit. One uses the generic rate estimator
which is supposed to measure average rate, the other is to use a token bucket
based packet counter. Well the generic rate estimator doesn't work correctly
in current kernels (no effect), so switch to using rate and burst.
Bugfix 3881
|
|
Bugfix 3833
Better help for configuration of match options
|
|
These two policy types didn't get fixed in change over to
policy management.
Bugfix 3829
|
|
It is confusing the default for ceiling for unclassified traffic is 100%
of available bandwidth, especially because there is no default ceiling
for other classes.
|
|
Need to check validity on update, not just create
|
|
This adds support for Qos using incoming policing. It is accepts the
syntax and processes commands, but is not fully debugged.
Bugfix: 3664
|
|
Recent CLI changes seem to have broken working templates that
do regex matching. Workaround this by doing the syntax checking
all in the perl script
Bugfix: 3553
|
|
Add new configuration support for plain fifo queueing.
Better code for the table in perl script that loads queue objects.
|
|
Since configuration system doesn't correctly notify on addition/deletion,
have to introduce this extra verbosity to have each traffic-shaper type
check for changes.
Bugfix for 3452
|
|
Add new QoS policy type "rate-limit" which is a wrapper around the
the Token Bucket Filter (TBF) qdisc.
Rate limit provides a simple way to do basic bandwidth limitation without
the complexity of the doing multiple classes in the traffic shaper
policy.
|
|
Conflicts:
templates/qos-policy/traffic-shaper/node.tag/class/node.tag/priority/node.def
templates/qos-policy/traffic-shaper/node.tag/default/priority/node.def
|
|
HTB in kernel only accepts 0-7 anything higher is rounded down to 7.
(see TC_HTB_NUMPRIO). Apply syntax checks to limit to that range
and add better help.
Fixes: 3098
|
|
- help strings standardized in vyatta-cfg-qos
|
|
Revert "More trivial stuff to wait for after freeze"
This reverts commit 2e81183ba5830f781c2e37246b6b59f82649fa3e.
|
|
Revert "Use uppercase when describing DSCP in help text"
This reverts commit e49e5b53411b50b1c8f13cded1641975f0443fde.
|
|
Trivial fix for Bug 2930
|
|
Add tab completion for values in /etc/protocols and completion help.
Bugfix: 2972
|
|
Bugfix: 2939
Add needed space for template.
|