Culmen Application Lanes

Route each kind of traffic to the uplink that suits it: games to the lowest-latency line, speed tests to the line you want measured, IPTV and live streaming to the lines with capacity for them.

Lanes included

• In-game — match and relay traffic for the major titles on the lowest-latency uplink, exempt from quota. Split-session games keep both halves together: PUBG Mobile's UDP gameplay and its TCP control side leave by the same exit
• Game downloads kept apart — patches and map packs take the cache or the normal path, so a 20 GB download never floods the low-latency line
• Speed tests — the control and data halves of a test pinned to the same line, so it measures one path instead of erroring on two
• IPTV — Xtream and Stalker panels on the line you choose, separated from speed tests even where both use the same port
• Live streaming — Twitch, YouTube Live and TikTok Live ingest sent out of the uplink with the upload
• Messaging and anti-bot sessions — WhatsApp kept on a local exit so users are not logged out, and sites behind anti-bot checks routed together with their challenge domains, on one line and one public IP
• Per-plan and per-window control — any lane can differ between plans, and between day and night

Why ports alone are not enough

One TCP port can belong to two services — speed-test servers and IPTV panels both use 8080, and every rule keyed on the port alone broke one of them. Lanes match on DNS names, learned TLS hostnames and provider prefixes first, use ports as the last resort, and resolve every overlap in a fixed, documented order.

RouterOS 7.x. Pairs with the Failover Engine, which moves a lane when its uplink fails.