QoS (Quality of Service)

QoS (Quality of Service) is a set of technologies that manage how network bandwidth is allocated across different types of traffic. When your router uses QoS, it ensures that real-time applications — gaming, video calls, VoIP — receive available bandwidth before less time-sensitive traffic like file downloads, cloud backups, or software updates.

Why QoS is needed

The problem QoS solves is competing traffic on a shared uplink. Every home network has a bottleneck: the WAN connection to the ISP. When multiple devices simultaneously use the internet, they all compete for that limited upstream and downstream capacity. Without QoS, the router uses a simple FIFO (first-in, first-out) queue — packets are forwarded in the order they arrive, with no consideration of their importance. A 4K video uploading in the background sends large bursts of data that fill the queue, causing packets from a simultaneous video call to wait behind them. The result is jitter and packet loss on the call, even if total bandwidth usage is below the plan's limit. QoS solves this by enforcing ordering and scheduling rules so that latency-sensitive packets jump ahead of bulk data.

How QoS works: classification, queuing, and shaping

Traffic classification is the first step — the router must identify what type of traffic each packet belongs to. Classification can be done by source/destination port (port 5004 = RTP audio), by IP address (your gaming console gets high priority), by protocol (UDP vs TCP), or by DSCP marking (see below). Queuing and scheduling is the mechanism that enforces priority: the router maintains separate queues for different traffic classes and uses a scheduling algorithm (WFQ, HFSC, HTB, or fq_codel) to decide which queue to serve next. High-priority queues are served first; lower-priority queues get leftover capacity. Policing and shaping enforce rate limits: policing drops packets that exceed a rate, while shaping buffers them for transmission at the allowed rate. Shaping is gentler — it smooths bursts without dropping packets — but adds queuing delay.

DSCP marking

DSCP (Differentiated Services Code Point) is a 6-bit field in the IP header that marks a packet's priority class. Common DSCP values: EF (Expedited Forwarding, value 46) for VoIP and real-time audio; AF41 (value 34) for video conferencing; CS0 (value 0) for best-effort traffic; CS1 (value 8) for background/bulk transfers. Applications and operating systems can set DSCP on outgoing packets — Windows, macOS, and Linux all support DSCP marking at the socket level. Routers that honour DSCP can then classify and queue traffic without having to inspect ports or payloads. In practice, many ISPs strip or ignore DSCP markings at their network boundary, so DSCP is most effective within your home network (LAN QoS) rather than end-to-end across the internet.

Traffic categories

• Voice / real-time audio: VoIP, Discord voice, game voice chat — requires very low latency (<50 ms) and minimal jitter; low bandwidth (64–128 Kbps per stream); highest priority
• Interactive video: Zoom, Teams, Google Meet, FaceTime — requires low latency and consistent throughput; 1–8 Mbps per stream; high priority
• Interactive data: Online gaming, remote desktop, SSH — latency-sensitive but low bandwidth; high priority
• Streaming video: Netflix, YouTube — tolerates 2–10 seconds of buffering; medium priority; large bandwidth consumer
• Background / bulk: Windows Update, cloud backup, BitTorrent, software downloads — not latency-sensitive; lowest priority; should yield to all other categories when link is congested

fq_codel and CAKE: modern home router QoS algorithms

fq_codel (Fair Queuing Controlled Delay) is an active queue management algorithm that addresses bufferbloat by maintaining many small per-flow queues and actively dropping packets when queue delay exceeds a target (typically 5 ms). It requires no manual configuration of traffic classes — it automatically gives each flow a fair share and keeps latency low by preventing any single flow from filling the buffer. CAKE (Common Applications Kept Enhanced) is a more advanced successor that combines fq_codel's per-flow queuing with an integrated traffic shaper, DSCP-aware tin classification, and host fairness (so one device cannot starve others even with many simultaneous flows). CAKE is available in OpenWrt, DD-WRT, and some commercial routers. Both algorithms are vastly superior to simple priority queuing for home use because they require minimal configuration and handle bursty traffic gracefully.

How to enable QoS on a home router

The location varies by router brand. On ASUS routers: Adaptive QoS under the QoS menu — enable it, select a mode (Traditional, Adaptive, or Bandwidth Limiter), and enter your measured upload/download speeds. On Netgear Nighthawk routers: Dynamic QoS under Advanced → Setup. On TP-Link routers: QoS under Advanced → QoS — enable and set bandwidth limits. On OpenWrt: install the luci-app-sqm package and configure SQM (Smart Queue Management) with the CAKE or fq_codel algorithm on your WAN interface.

The most common QoS mistake: wrong bandwidth settings

QoS only works correctly when the router's shaper enforces a rate slightly below the actual WAN link speed. If you enter your plan's advertised speed (e.g., 500 Mbps) as the QoS bandwidth limit, but your actual delivered speed is 480 Mbps, the shaper will not engage because it thinks there is still headroom. The router's physical WAN queue will fill instead, causing bufferbloat that QoS cannot fix. The correct approach: run a speed test, take the result (not the plan speed), and set QoS bandwidth to 90–95% of that measured value. This ensures the router's shaper is always the controlling bottleneck, giving it full control over queue discipline.

QoS vs traffic shaping vs policing

QoS is the broad umbrella term covering all techniques for managing traffic quality — classification, queuing, scheduling, shaping, and policing. Traffic shaping specifically refers to rate-limiting outgoing traffic by buffering excess packets and releasing them at the allowed rate — it smooths bursts without dropping packets. Policing enforces rate limits by dropping (or remarking) packets that exceed the limit — it does not buffer, so it is used at network ingress points where buffering would add unacceptable delay. At home, you want shaping (not policing) on your WAN interface because shaping prevents the ISP's modem buffer from filling while still delivering all your data.

Frequently Asked Questions

Does QoS increase my internet speed?

No — QoS does not increase total bandwidth. It manages how existing bandwidth is distributed. If your connection is below your needs, QoS helps prioritise what matters but cannot create capacity that does not exist.

Should I use QoS on a gigabit connection?

Generally not needed. QoS benefits are most apparent when the connection is regularly near saturation. On a gigabit plan, it is rare for background tasks to meaningfully impact real-time traffic. QoS matters most on 100–300 Mbps plans with multiple heavy users.