Traffic shaping and QoS
Firecradle's traffic shaping engine applies bandwidth limiters, hierarchical priority queues, and per-flow classification on every interface - so voice and video stay smooth while bulk transfers get out of the way, without proprietary hardware or a separate license.
- Predictable bandwidth for business-critical applications
- VoIP and video calls prioritized automatically with one-click presets
- No separate QoS license or add-on hardware
- Same engine and console across every appliance
- Full control over limiters, queues, and classification rules
- DSCP marking and priority bands per rule
- Per-interface, per-direction, and per-IP shaping
- Egress shaping native; ingress shaping supported per interface
- One-click presets: VoIP priority, ACK prioritization, gaming low-latency
- Live per-queue stats: sent, dropped, and backlog
- Enable or disable a rule without deleting it
- Centralized rule management from the cloud dashboard
Four Building Blocks of Traffic Shaping
Combine limiters, queues, and classification rules to express anything from a simple per-VLAN bandwidth cap to a full voice-and-video priority hierarchy.
No Manual Curve Math Required
Hierarchical queue scheduling can mean hand-tuning service curves - not on Firecradle. Built-in presets seed a working queue tree and classification rules for the traffic patterns that matter most, so you get priority handling in one click instead of an afternoon of tuning.
See What Each Queue Is Actually Doing
Every limiter and queue reports live sent, dropped, and backlog counters, so you can confirm a preset is actually protecting voice traffic instead of just assuming it. Egress shaping runs natively on the interface; ingress shaping is applied through a mirrored path so both directions can be shaped without dropping legitimate traffic.
- Per-interface limiters, applied in either direction or both
- Per-IP bandwidth masking for shared connections
- Enable or disable a queue or rule without deleting it
- Stats refresh live - no separate monitoring tool required
| Queue | Sent | Dropped | Backlog |
|---|---|---|---|
| voip | 184 MB / 210,442 pkts | 0 | 0 B |
| default | 9.8 GB / 6,204,118 pkts | 1,204 | 12 KB |
| bulk | 41.2 GB / 22,910,553 pkts | 58,340 | 96 KB |
Real-World Use Cases
VoIP Call Quality During Peak Hours
Challenge: Softphone calls get choppy whenever a large file transfer or software update saturates the office WAN link.
Capping Guest Wi-Fi Bandwidth
Challenge: Guest network usage occasionally saturates the uplink, slowing down business-critical traffic on the same connection.