Wireless ISPs

Keep busy-hour service responsive across APs and backhauls

Control shared capacity at the constrained branch, keep subscribers fair, and give support a path from a busy tower to the affected circuit.

Give the shared bottleneck its own limit

Illustrative download limits, not sizing recommendations. Active circuits compete within each configured parent limit, even when their individual plan rates add up to more.

  1. 01Backhaul: 500 Mbps

    An explicit limit on this part of the configured path.

  2. 02Tower: 300 Mbps

    An explicit limit on this part of the configured path.

  3. 03Access point: 200 Mbps

    An explicit limit on this part of the configured path.

  4. 04Competing circuits: 100 Mbps each

    CAKE manages competing flows within each circuit.

Control the shared bottleneck

Nest subscriber circuits beneath AP, site, and backhaul limits so a constrained branch has an explicit shaping envelope.

  • Set capacity at each shared parent
  • Inspect configured and effective limits
  • Keep the rest of the hierarchy in view

Keep subscribers fair under load

Per-circuit queue management separates competing flows while the parent hierarchy enforces shared capacity.

  • CAKE fairness inside each circuit
  • Subscriber min/max rates from your source of truth
  • Queue and throughput evidence during busy hour

Follow a complaint to its branch

Start with the affected site, compare its children, and open the subscriber circuit before deciding where to intervene.

  • Compare RTT and retransmits with utilization
  • Inspect the circuit and its upstream path
  • Use Insight history to check when the pattern began

Local operator console

Check the parent, then follow its circuits

Compare configured and effective limits with live quality signals. Follow the affected branch into circuit investigation, then use Insight history when the problem has already passed.

LibreQoS v2.2 Network Tree: configured and effective limits, live throughput, RTT, QoO, and child node queue metrics
Actual LibreQoS v2.2 Network Tree. This product view illustrates the workflow; the capacity example above is separate. · Open full-size product view ↗

Walkthrough

See the wireless ISP workflow in practice

These views show topology, map, and tree context that help WISPs locate congestion and support issues faster.

LibreQoS site map
LibreQoS site map
LibreQoS network tree
LibreQoS network tree

Plan your pilot

Put the workflow to work

Deploy

Validate LibreQoS on your network

Start with a limited pilot, compare the same load conditions, and confirm the affected branch and circuit behavior before expanding.