summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Poessinger <christian@poessinger.com>2020-07-21 22:30:07 +0200
committerGitHub <noreply@github.com>2020-07-21 22:30:07 +0200
commit726025e4f5dac9e5a327b9c5b331d8acf2c8ce08 (patch)
tree900eba4a11b5a56acbf91f001fa8b2f5c1ac4ae9
parent499a1c59fbb64a4b336cfc7edf8802399a9dae91 (diff)
parent7fdc8e58ee3ac18c5a109ff80e89acb6174a5ef4 (diff)
downloadvyos-documentation-726025e4f5dac9e5a327b9c5b331d8acf2c8ce08.tar.gz
vyos-documentation-726025e4f5dac9e5a327b9c5b331d8acf2c8ce08.zip
Merge pull request #290 from hlmtre/patch-2
Correct small typos; add matching examples
-rw-r--r--docs/qos.rst20
1 files changed, 15 insertions, 5 deletions
diff --git a/docs/qos.rst b/docs/qos.rst
index c0266461..0a58e3f8 100644
--- a/docs/qos.rst
+++ b/docs/qos.rst
@@ -1086,7 +1086,7 @@ parameters.
Example
^^^^^^^
-A simple example of Shaper using priorities.
+A simple example of Shaper using priorities. It includes examples of matching on addresses and protocols.
.. code-block:: none
@@ -1111,7 +1111,17 @@ A simple example of Shaper using priorities.
set traffic-policy shaper MY-HTB default ceiling '100%'
set traffic-policy shaper MY-HTB default priority '7'
set traffic-policy shaper MY-HTB default queue-type 'fair-queue'
-
+ set traffic-policy shaper MY-HTB class 2 match ack ip tcp ack
+ set traffic-policy shaper MY-HTB class 2 match dns ip destination port '53'
+ set traffic-policy shaper MY-HTB class 2 match icmp ip protocol 'icmp'
+ set traffic-policy shaper MY-HTB class 2 match ssh ip destination port '22'
+ set traffic-policy shaper MY-HTB class 2 match syn ip tcp syn
+ set traffic-policy shaper MY-HTB class 2 priority '5'
+ set traffic-policy shaper MY-HTB class 2 queue-limit '16'
+ set traffic-policy shaper MY-HTB class 2 queue-type 'fair-queue'
+ set traffic-policy shaper MY-HTB class 5 bandwidth '10%'
+ set traffic-policy shaper MY-HTB class 5 burst '15k'
+ set traffic-policy shaper MY-HTB class 5 ceiling '100%'
.. _ingress-shaping:
@@ -1153,7 +1163,7 @@ Once a traffic-policy is created, you can apply it to an interface:
.. code-block:: none
- set interfaces etherhet eth0 traffic-policy out WAN-OUT
+ set interfaces ethernet eth0 traffic-policy out WAN-OUT
You can only apply one policy per interface and direction, but you can
have several policies working at the same time:
@@ -1161,8 +1171,8 @@ have several policies working at the same time:
.. code-block:: none
set interfaces ethernet eth0 traffic-policy in WAN-IN
- set interfaces etherhet eth0 traffic-policy out WAN-OUT
- set interfaces etherhet eth1 traffic-policy out WAN-OUT
+ set interfaces ethernet eth0 traffic-policy out WAN-OUT
+ set interfaces ethernet eth1 traffic-policy out WAN-OUT
set interfaces ethernet eth2 traffic-policy out LAN-IN
set interfaces ethernet eth2 traffic-policy out LAN-OUT