IntenseWebs/LibreQoS
3
0 Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2026-11-01 15:53:02 -06:00
Code Issues Packages Projects Releases Wiki Activity

Update design.md

Browse Source
This commit is contained in:
Robert Chacón authored and GitHub committed 2025-05-10 15:47:41 -06:00
1 parent efab0d90f3
commit e22650b5bf
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
docs/v2.0/design.md
+1 -1
View File
@@ -8,7 +8,7 @@
### Primary and Backup Paths
We recommend using dynamic routing protocols such as OSPF to create a high cost and low cost path between the edge router and core distribution router/switch. The low cost path should pass "through" the LibreQos shaper bridge interfaces to allow LibreQoS to see and shape traffic. For example, a low cost OSPF path may be set to a value of 1. The high-cost (backup) link would completely bypass LibreQoS, being set to a higher cost (perhaps 100 for OSPF) to ensure that traffic only takes that path when the LibreQoS shaper bridge is not operational.
We recommend using dynamic routing protocols such as OSPF to create a high cost and low cost path between the edge router and core distribution router/switch. The low cost path should pass "through" the LibreQoS shaper bridge interfaces to allow LibreQoS to observe and shape traffic. For example, a low cost OSPF path may be set to a value of 1. The high-cost (backup) link would completely bypass LibreQoS, being set to a higher cost (perhaps 100 for OSPF) to ensure that traffic only takes that path when the LibreQoS shaper bridge is not operational.
### NAT/CG-NAT
If you use NAT/CG-NAT, please place LibreQoS inline prior to where NAT is applied, as LibreQoS needs to shape pre-NAT addresses (100.64.0.0/12) not public post-NAT IPs.