mirror of
https://github.com/LibreQoE/LibreQoS.git
synced 2026-11-02 08:10:02 -06:00
Update update.md
This commit is contained in:
1 parent
dd56833705
commit
0bd7a6075e
1 file changed
+1
-3
+1
-3
@@ -7,9 +7,7 @@ If you use the XDP bridge, traffic will briefly stop passing through the bridge
|
||||
## If you installed the .deb
|
||||
|
||||
```{important}
|
||||
Starting in v2.0, mapped-circuit ingest depends on valid entitled license/grant state. Without a valid Insight or Local license/grant state, LibreQoS reads only the first 1000 valid mapped circuits into active shaping state. This includes expired or otherwise invalid local grant/license state. See [Insight Licensing Behavior](insight.md#mapped-circuit-limits-and-license-state) and [Troubleshooting](troubleshooting.md).
|
||||
|
||||
Starting in v2.2, the Node API uses the same mapped-circuit policy. Networks with 1,000 or fewer valid mapped circuits may use the API without an Insight subscription; larger networks require a valid API or Insight entitlement. API calls remain authenticated. Administrators can create up to 16 named local API keys in **License & Services**; keys are shown once, stored only as SHA-256 digests, and can be revoked. Existing license keys and the legacy local bearer token remain compatible, and key changes may take up to 30 seconds to take effect.
|
||||
Starting in v2.0, mapped-circuit ingest depends on a [valid license](https://libreqos.com/pricing). Without a valid Insight or Local license, LibreQoS reads only the first 1000 valid mapped circuits into active shaping state. See [Insight Licensing Behavior](insight.md#mapped-circuit-limits-and-license-state) and [Troubleshooting](troubleshooting.md). The Node API uses the same mapped-circuit policy: networks with 1,000 or fewer valid mapped circuits may use the API without an Insight subscription; larger networks require a valid license.
|
||||
```
|
||||
|
||||
Run:
|
||||
|
||||
Reference in new issue
Block a user