Practical, step-by-step recipes for the jobs people actually ask us about — prioritizing the register over the guest network, keeping calls smooth, extending a VLAN across sites, and diagnosing a bonded link that feels slow. Each recipe uses the real Balance UI and InControl screens.
Prioritize POS Over Guest Wi-Fi
Registers must never stall because a customer is streaming on the guest network. The pattern is three layers: separate the traffic, guarantee POS its bandwidth, and steer POS to the most reliable path.
Open recipe →QoS for VoIP & Video Calls
Real-time audio and video are unforgiving of jitter and loss. Two moves fix it: prioritize the traffic with an application queue, and put it on a SpeedFusion path that hides packet loss.
Open recipe →Extend a VLAN Across Sites
Sometimes gear at a remote site needs to be on the <em>same</em> subnet as the main site — a production LAN, an AV setup, or an application that assumes a flat network. SpeedFusion Layer-2 bridging does exactly that.
Open recipe →Drop-In Mode
You don't have to rip out your existing firewall or renumber the network to gain bonding. In <strong>drop-in mode</strong> the Peplink sits transparently between your ISP handoff and your current firewall, keeps your public IP, and adds as many links as you want behind it.
Open recipe →What Kit for My Site?
The right kit is about how many independent paths you need and how much you bond. A rough guide:
Open recipe →SpeedFusion Slow or Unstable?
When a bonded link feels slow or unstable, work it in order — isolate which path is bad, then apply the matching fix. Here's the decision tree we use.
Open recipe →New: When NOT to Bond: an Honest Sizing Guide → When simple dual-WAN failover plus monitoring genuinely beats a bonded build — and what good failover still requires.