This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
qos-settings [2024/04/10 21:34] – -grammar, formatting hogwild | qos-settings [2024/04/16 16:55] (current) – [How Does all this Help Me?] remove "of the" hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== QoS Principles ====== | + | ====== QoS - Basic Principles ====== |
- | Quality of Service (QoS) is a method to prioritize/ | + | Quality of Service (QoS) is a method to prioritize/ |
- | * Identifies traffic | + | ==== QoS is not Bandwidth Limiter ==== |
- | * Classifies this traffic | + | |
- | * Marks packets | + | |
- | * Defines classes and subclasses | + | |
- | * Set class parameters (such as reserved bandwidth) | + | |
- | \\ You might have heard the above points when describing " | + | QoS is not the same as FreshTomato's [[bwlimit|Bandwidth Limiter]]. \\ |
- | It's often said that the QoS is a technique to mitigate lack of bandwidth when an upgrade is too costly or even impossible. More precisely, QoS also allows you to prioritize latency-sensitive | + | * QoS analyzes all traffic |
+ | * QoS follows rules for prioritizing one type of traffic | ||
+ | * Bandwidth Limiter limits the bandwidth used by one or more client devices on the network. | ||
+ | * Bandwidth Limiter prioritizes one client device/ | ||
- | Here is some commonly used QoS terminology: | + | \\ |
- | * **Traffic: | + | If you need a simple, crude tool for one or more known client devices, Bandwidth Limiter may be all that you need. |
- | * **Best effort:** This is also referred to as "no QoS". This works on the principle of "first come first served" | + | |
- | * **Classification: | + | |
- | * **Marking: | + | |
- | * **Queuing: | + | |
- | * **Policing: | + | |
- | * **Class Discipline**: | + | |
- | \\ Looking at the list above let's put everything together: | + | QoS is a more sophisticated, |
- | ==== What does this mean all mean to me? ==== | + | However, Bandwidth Limiter shares a few settings with QoS. When Bandwidth Limiter is enabled, QoS should be disabled, and vice versa. If both are enabled, they will conflict with each other and neither will work. \\ |
- | Ever experienced a poor VoIP call from your LAN into Internet? Do you get media buffering | + | Basically, QoS performs the following: |
+ | |||
+ | * Identifies traffic. | ||
+ | * Classifies this traffic. | ||
+ | * Marks packets. | ||
+ | * Defines classes and subclasses. | ||
+ | * Sets class parameters (such as reserved bandwidth). | ||
+ | |||
+ | \\ You might have heard the above points when describing " | ||
+ | |||
+ | It's often said that QoS is a technique to mitigate lack of bandwidth when an upgrade is too costly or even impossible. More precisely, QoS also allows you to prioritize latency-sensitive traffic (such as voice) even when there' | ||
+ | |||
+ | Here are some commonly used QoS terms:\\ | ||
+ | |||
+ | * **Traffic: | ||
+ | * **Best effort:** This is also known as "no QoS" or "first come, first served" | ||
+ | * **Classification: | ||
+ | * **Marking: | ||
+ | * **Queuing: | ||
+ | * **Policing: | ||
+ | * **Queuing Discipline: | ||
+ | * asdfgjkl | ||
+ | * asdfghjkl\\ | ||
+ | |||
+ | \\ The diagram below should help you to understand these principles: | ||
+ | |||
+ | |||
+ | ==== How Does all this Help Me? ==== | ||
+ | |||
+ | Have you ever experienced a poor quality | ||
+ | |||
+ | Do your media, such as videos, buffer | ||
+ | |||
+ | Is someone on your LAN generating too much traffic? | ||
+ | |||
+ | These are all problems that QoS can help you to solve. Note that QoS is NOT auto-regulating. You need to manually | ||
===== CTF implications ===== | ===== CTF implications ===== | ||
Line 37: | Line 65: | ||
\\ | \\ | ||
- | \\ | + | |