diff options
author | currite <sll@disroot.org> | 2020-08-04 20:14:11 +0200 |
---|---|---|
committer | currite <sll@disroot.org> | 2020-08-04 20:14:11 +0200 |
commit | f1c38b133517baca9fdc1d7c3c74c314664cc992 (patch) | |
tree | 1e7a922e6afe93876657bdbd252c43945a5c78ff | |
parent | 243238380a6d408d40ef5e64b9d4222c3898e264 (diff) | |
download | vyos-documentation-f1c38b133517baca9fdc1d7c3c74c314664cc992.tar.gz vyos-documentation-f1c38b133517baca9fdc1d7c3c74c314664cc992.zip |
qos: move ingress shaping to the end of the article
Ingress Shaping is an exceptional case, it should be shown after it is explained how
the standard procedure works.
-rw-r--r-- | docs/qos.rst | 62 |
1 files changed, 32 insertions, 30 deletions
diff --git a/docs/qos.rst b/docs/qos.rst index c0266461..05e66ba4 100644 --- a/docs/qos.rst +++ b/docs/qos.rst @@ -1114,6 +1114,38 @@ A simple example of Shaper using priorities. +Applying a traffic policy +========================= + +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 + +You can only apply one policy per interface and direction, but you can +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 eth2 traffic-policy out LAN-IN + set interfaces ethernet eth2 traffic-policy out LAN-OUT + + +Getting queueing information +---------------------------- + +.. opcmd:: show queueing <interface-type> <interface-name> + + Use this command to see the queueing information for an interface. + You will be able to see a packet counter (Sent, Dropped, Overlimit + and Backlog) per policy and class configured. + + + .. _ingress-shaping: The case of ingress shaping @@ -1146,36 +1178,6 @@ That is how it is possible to do the so-called "ingress shaping". -Applying a traffic policy -========================= - -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 - -You can only apply one policy per interface and direction, but you can -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 eth2 traffic-policy out LAN-IN - set interfaces ethernet eth2 traffic-policy out LAN-OUT - - -Getting queueing information ----------------------------- - -.. opcmd:: show queueing <interface-type> <interface-name> - - Use this command to see the queueing information for an interface. - You will be able to see a packet counter (Sent, Dropped, Overlimit - and Backlog) per policy and class configured. - .. _that can give you a great deal of flexibility: https://blog.vyos.io/using-the-policy-route-and-packet-marking-for-custom-qos-matches .. _tc: https://en.wikipedia.org/wiki/Tc_(Linux) |