Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dpi:dpi_options:opt_bandwidth_mgmt:bandwidth_description [2020/02/05 17:31] – ↷ Page moved from en:dpi:dpi_options:base_functionality:opt_bandwidth_mgmt:bandwidth_description to en:dpi:dpi_options:opt_bandwidth_mgmt:bandwidth_description lexx26 | en:dpi:dpi_options:opt_bandwidth_mgmt:bandwidth_description [2025/09/22 07:51] (current) – elena.krasnobryzh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== General description ====== | ====== General description ====== | ||
| + | {{indexmenu_n> | ||
| + | Subscriber traffic is defined by a list of IP addresses or CIDR. Subscriber traffic can have [[en: | ||
| + | |||
| + | Policing is applied to 8 traffic classes, configured via [[en: | ||
| + | <note important> | ||
| + | This approach makes it possible to combine external and internal policers in a compatible way. | ||
| + | </ | ||
| + | |||
| + | Two policing mechanisms are available to choose from: | ||
| + | - TBF without hierarchy ([[https:// | ||
| + | - HTB with hierarchy for 8 classes ([[http:// | ||
| + | |||
| + | Creation and assignment of policing (tariff plan) is performed via [[en: | ||
| + | |||
| + | Applying tariff plans to a subscriber is possible either [[en: | ||
| + | |||