Keep guest WiFi fair across rooms and devices
Give hospitality teams control of shared capacity and a clear path from a guest complaint to the affected property segment and circuit.
Conceptual example. Parent groups and circuit mapping come from your network configuration.
- 01Property WAN
Shared capacity
- 02Floor / wing
Stable parent group
- 03Room or device
Configured IP-to-circuit mapping
- 04Guest flows
Fair queueing
Match fairness to the addressing model
Use per-device circuits where device IP mapping is stable. Room or subnet grouping can reduce circuit count where appropriate.
- Explicit device/address mapping
- Per-circuit CAKE
- Stable floor or wing parents
Trace a guest complaint
Compare the circuit with its floor or wing, review parent capacity, and correlate transport evidence with your WiFi tools.
- Identify broad versus isolated symptoms
- Inspect RTT, retransmits, and queue pressure
- Escalate with the relevant time and segment
Size for occupied-device demand
Per-device shaping increases active circuit and queue count. Validate RAM, queue pressure, and throughput using a representative pilot.
- Count mapped device circuits
- Measure under peak occupancy assumptions
- Use room/subnet grouping if guardrails are reached
Operator workflow
Keep property context during the investigation
Read the site timeline, identify the interval of degraded service, and inspect the affected segment and circuit. The product view is illustrative of the workflow.
Walkthrough
See the hospitality support workflow
These views show dashboard, site, and map context that help operators move from property-wide symptom into the affected segment.
Plan your pilot
Put the workflow to work
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.