QuickQ guide

This guide matches client v5.2.0. It covers protocol choice, installation on every platform, routing configuration, IPv6 handling and a structured troubleshooting order. Each chapter stands on its own.

Applies to v5.2.0Last updated 2026-10-13About 13 minutes

1. Choosing a protocol

The client ships WireGuard, IKEv2 and OpenVPN with unmodified implementations. Choose by network environment, not by security level.

Transport characteristics and typical use
ProtocolTransportLatency and throughputTypical use
WireGuardUDPBestDefault choice: gaming, streaming, everyday use
IKEv2UDP 500/4500ExcellentCorporate or campus networks, frequent handover
OpenVPNTCP 443FairHeavily restricted networks that only allow 443

Order to try: WireGuard first; move to IKEv2 if it will not connect or keeps dropping; only consider OpenVPN over TCP if IKEv2 cannot complete a handshake either. The client remembers your last choice.

2. Windows setup

Supports Windows 10 1809 or later and Windows 11 on 64-bit. Setup creates a virtual network adapter, which acceleration requires.

Installation

  1. Download QuickQ-Setup-5.2.0-x64.exe from the downloads page;
  2. Run certutil -hashfile QuickQ-Setup-5.2.0-x64.exe SHA256 to verify it;
  3. Run the installer and allow the virtual adapter driver;
  4. Launch the client and register with an email address.

Settings worth adjusting

  • Protocol: WireGuard by default; IKEv2 on corporate or campus networks.
  • Disconnect protection: keep it on so traffic freezes if the tunnel drops.
  • Launch at start-up: useful on machines you use every day.
  • Quality panel: shows link saving and jitter in the tray.

3. macOS setup

The universal package runs natively on Apple Silicon and Intel, takes over traffic through a system network extension and coexists with iCloud Private Relay.

  1. Download QuickQ-5.2.0-universal.dmg and verify its SHA-256;
  2. Open the disk image and drag QuickQ into Applications;
  3. Allow the network extension under System Settings → Privacy & Security on first launch;
  4. Sign in and connect from the menu bar, where nodes and protocols can be switched directly.

If the prompt never appears: run sudo killall -HUP mDNSResponder in Terminal to refresh network services, then reopen the client.

4. Mobile setup

Mobile clients default to ChaCha20-Poly1305, which is easier on mobile silicon than AES.

iOS / iPadOS (15.0 and later)

  1. Search for QuickQ on the App Store, or use this site's link;
  2. Allow the VPN configuration on first connect;
  3. Enable Background App Refresh so it recovers after a network change;
  4. Turn on battery saver if you want to reduce the impact further.

Android (11.0 and later)

  1. Install from Google Play, or download the APK from this site;
  2. Allow installation from that source when using the APK;
  3. Authorise the VPN service on first connect;
  4. Set QuickQ to Unrestricted under Settings → Battery.

5. Routers and command line

Covering TVs, consoles and smart home devices is easiest at the router: configure once and the whole network benefits.

# install curl -fsSL https://dl.quickqwork.com/setup.sh | sh # sign in and probe Hong Kong peering points quickq-cli login quickq-cli peers --region hk # connect to a peering point as a daemon quickq-cli up --peer hkg-02 --daemon

OpenWrt router

  1. Confirm the firmware is OpenWrt 22.03 or later;
  2. Install quickq-core and luci-app-quickq from System → Software;
  3. Open the QuickQ menu in LuCI and enter the device key from the account centre;
  4. Under policy routing, choose the devices or subnets that should use the tunnel.

Performance note: the router CPU is often the bottleneck. For several high-bandwidth devices at once, pick a model with hardware forwarding acceleration or enable acceleration selectively.

6. Routing rules

Routing rules exist so that turning on acceleration does not force every local request through a detour. Two match types are available and can be mixed.

When to use domain rules

  • Only one website should be accelerated while the rest stays direct;
  • The target is a web service that calls several subdomains;
  • A process needs both intranet and internet access, so per-process rules would misfire.

When to use per-process rules

  • Games, call software or design tools that need the whole application accelerated;
  • Precision matters and the browser on the same machine should stay direct;
  • The process contacts many random domains, making domain rules impractical.

Suggested approach: add one direct rule for the local NAS, printers, intranet systems and admin consoles, then add the applications that need acceleration one by one. Rules sync across your devices.

7. IPv6 dual stack

Networks fall into three categories: IPv4-only, dual stack and IPv6-only. The client detects the situation and negotiates accordingly, normally without manual intervention.

  • Dual stack: IPv6 direct peering is preferred, cutting average link time by a further 9%.
  • IPv6 only: address translation is automatic, with no tunnel or gateway configuration.
  • IPv4 only: standard negotiation, no functional difference.
  • Leak protection: IPv6 leak protection is on by default to stop traffic bypassing the tunnel.

To confirm which family is in use, check the data path line in the client's connection details.

8. Diagnostics

Work through the order below. Reinstalling the client first is a mistake — it usually destroys the evidence you need.

Step 1: confirm the local network

With acceleration off, can you load ordinary websites? If not, the problem is local.

Step 2: change protocol

Move from WireGuard to IKEv2. Many failures are simply a network that shapes UDP.

Step 3: change peering point

Check the link saving figure. Under 40 ms means limited benefit, so switch to a point with a higher figure.

Step 4: rule out conflicts

Close other proxy extensions, the traffic filtering modules of enterprise security suites, and anything else that rewrites the system routing table.

Step 5: export a report

Use Settings → Export diagnostic report and send the file to the contact page with your OS version, client version, protocol, peering point and the time the problem started. The report contains no access records.

9. Terminology

Direct peering point
An interconnection with the local carrier network where traffic leaves the local network, taking fewer hops than routing through a central facility.
Link saving
The round-trip time saved relative to a direct connection, shown in the client to judge whether the current point is worth keeping.
Per-session scheduling
Migrating a single connection to another exit rather than switching the whole device, so one congested exit does not slow everything.
Dual stack
A network supporting IPv4 and IPv6 simultaneously, where the client negotiates the better family first.
Disconnect protection
Freezing network access when the tunnel drops unexpectedly, to avoid exposing your real address.
Routing rules
Deciding by domain or process which traffic uses the tunnel and which stays direct.

Not covered here? Start a conversation on the contact page, or check the help centre for specific scenarios.