Keep shipboard WiFi responsive as WAN capacity changes
Combine shared-capacity fairness, configurable StormGuard behavior, and circuit evidence for cruise and maritime networks with variable upstream headroom.
Conceptual example. Parent groups and circuit mapping come from your network configuration.
- 01Variable WAN
Available capacity changes
- 02Ship / shared parent
StormGuard within configured limits
- 03Deck / circuit
Stable configured grouping
- 04Onboard flows
Fair queueing
Adapt the configured shaping envelope
The maritime recipe targets one vessel with one variable WAN capacity domain. StormGuard adjusts the top-level WAN node within configured guardrails using observed congestion signals.
- Explicit minimum and maximum bounds
- One top-level WAN control target
- A documented validation and rollback path
Control added queue delay
Fair queueing helps prevent competing traffic from building excessive queues on the constrained path. Propagation delay still remains part of the connection.
- Shared parent capacity
- Per-circuit fairness
- Loaded RTT alongside throughput
Investigate from ship to circuit
Use local evidence for the current node and Insight history to compare intervals and shapers before changing capacity or escalating upstream.
- Segment and circuit scope
- ASN and timeline context
- A pilot using realistic WAN variation
Operator workflow
Choose the segment before changing the WAN envelope
Compare site and circuit behavior over the same time interval. Product views illustrate the investigation; they do not represent a measured shipboard deployment.
Walkthrough
See the maritime operator workflow
These views show ranking, map, and globe context that help teams understand where limited onboard capacity is degrading first.
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.