summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Poessinger <christian@poessinger.com>2020-09-15 19:09:08 +0200
committerGitHub <noreply@github.com>2020-09-15 19:09:08 +0200
commit4131c411e60b121f63c83638df031ac35e9f7b8d (patch)
treef085cd230cf78febe81c8961d936166584e0dd66
parent7c9212f7826e45577d6cfa6f4675b0c82a38d31d (diff)
parentfc94b0cfd7682fc9eacc4fbe506cd55744759703 (diff)
downloadvyos-documentation-4131c411e60b121f63c83638df031ac35e9f7b8d.tar.gz
vyos-documentation-4131c411e60b121f63c83638df031ac35e9f7b8d.zip
Merge pull request #325 from currite/qos-hint
qos: improve hint on choosing policy
-rw-r--r--docs/qos.rst11
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/qos.rst b/docs/qos.rst
index a4e56665..3cd183cf 100644
--- a/docs/qos.rst
+++ b/docs/qos.rst
@@ -336,12 +336,11 @@ you will only be able to apply one policy per interface and direction
Some policies can be combined, you will be able to embed_ a different
policy that will be applied to a class of the main policy.
-.. hint:: If you are looking for a policy for your outbound traffic but
- you do not know what policy you need, you might consider FQ-CoDel_ as
- your multipurpose nearly-no-configuration low-delay fair-queue
- policy; if delay does not worry you and you want to manually allocate
- bandwidth shares to specific traffic, then you should consider
- Shaper_.
+.. hint:: **If you are looking for a policy for your outbound traffic**
+ but you don't know which one you need and you don't want to go
+ through every possible policy shown here, **our bet is that highly
+ likely you are looking for a** Shaper_ **policy and you want to**
+ :ref:`set its queues <embed>` **as FQ-CoDel**.
Drop Tail
---------