| Age | Commit message (Collapse) | Author |
|---|
|
Need to check validity on update, not just create
|
|
The bandwidth value needs to be validated and converted if necessary.
|
|
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.
|
|
Later versions of vyatta-iproute are named iproute, and are
identified by version.
|
|
|
|
Need to handle the case of devices that don't know their current speed.
In this case, ethtool will print "Unknown!" which the old code wasn't
handling right.
Move the default speed stuff down into traffic shaper code as well,
so any future policies using auto can make other choices as to what
to do in this case.
Bugfix: 3450
|
|
When validating the class rates, need to leave the array of
classes in original form for later command processing.
Bugfix 3458
|
|
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
|
|
|
|
Bugfix 3450
If device is offline, can't find speed. So use a sensible default
and try a few times.
|
|
Should say "greater or equal" not "less than"
Bug 2919
|
|
Bugfix 2919
As long as the bandwidth isn't auto, then validate at commit time.
|
|
|
|
Add newline in right spot so words don't run together.
|
|
One more try at explaining why rates must be correct.
|
|
Use speed of underlying interface. Bug 3137
|
|
Use tcindex to get original dsfield value.
Fixes bug: 3033
|
|
This might resolve issues with set-dscp and later dscp matches.
|
|
|
|
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.
|
|
One of the parameters to TrafficShaper::_define was not being passed
or used.
|
|
Change the existing warning into a failure. No one reads warnings,
and the shaping is unstable if ceiling < bandwidth.
|
|
|
|
|
|
|
|
|
|
ATM interfaces on ADSL, and PPPOE on ethernet interfaces.
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
Slightly better message for the case of using auto value for bandwidth
on a device does not support it.
Bug: 3104
|
|
|
|
Yet another place where id needs to be converted to hex.
Should fix bug 3078.
|
|
This fixes problem which causes QoS not to fail on commit if ceiling
is a percentage.
The ceiling maybe a percentage (not fixed) value so it needs to
be interpreted before passing to tc.
|
|
- help strings standardized in vyatta-cfg-qos
|
|
Internal TC commands use hex for identifiers and one place in perl
script forgot to reformat.
Bugfix for 3142 from Chris Smith <chris.smith@conceptcoders.com>
|
|
|
|
Add template and configuration support for QoS policy over vif.
This is covers bug 3137
|
|
Test version
|
|
|
|
ceiling parameter was not being forwarded to kernel.
|
|
If the customer has incorrectly assigned bandwidth and
rate ceilings for QOS, the problem can not be detected until
commit. At that point (possibly during boot), it is better to
print a warning rather than failing.
This addresses Bug 2919.
|
|
|
|
|
