Traffic Routes
Send everyone from a country or network to one node or CDN
A traffic route sends every redirect for viewers from chosen countries or networks to one edge node or CDN, whatever host the redirect pointed at. Where a URL replacement needs a "From URL" per origin host, a route needs none: it rewrites the host of any redirect the gateway sees.
Create a route
- Open Traffic Routes in the server's config section and click Edit.
- Add route, then add the countries and/or networks (ASNs) it should
match. A network entry is
ASN15169from the picker, or a fragment of the AS name such asCOMCAST. - Pick the destination: an edge node IP or a CDN.
- Save.
Priority
Routes and replacements share one ladder, and the most specific rule wins. A network match beats a country match, and within the same level a rule written for the redirect's own host beats an any-host route:
| Priority | Rule | Matches on |
|---|---|---|
| 1 | ASN replacement for the redirect's host | host + network |
| 2 | Route matched by network (ASN) | network |
| 3 | URL replacement, country entry for the host | host + country |
| 4 | Route matched by country | country |
| 5 | URL replacement, default entry for the host | host only |
In practice a route is the catch-all: it takes every redirect host that has no replacement rule of its own for that country or network, and it beats a host's plain default. If you want a route to take a host that already has a country entry, delete that entry.
Example: a route sends Germany to node A. A VOD host has a URL replacement whose Germany entry points at node V, and an ASN replacement sends Telekom (AS3320) viewers of the live host to node B. A German Telekom viewer on the live host goes to node B. A German viewer on the VOD host goes to node V. A German viewer on any other host goes to node A.
Within one level, the first matching route in the list applies, so order routes from most to least specific.
How it is applied
- The port, path and query of the redirect are kept, so the edge node must listen on the same port as the original host, as with replacements.
- Redirects that point back at the panel itself (the port's backend host) are never routed, and relative redirects are left alone.
- Excluded users bypass routes, as they bypass country rules. They get the host's default replacement, or nothing at all when Keep the original host is on (Excluded Users page).
- If the route's destination is a CDN with every node offline, or a CDN that no longer exists, the route is skipped and normal replacements run.
Example
Germany, Austria → frankfurt-vps
ASN7922 (Comcast) → cdn: US poolA viewer in Austria on Comcast is sent to the US pool: the network match wins. If a host also had an ASN replacement for Comcast, that host would follow the replacement instead, because a rule for the host itself beats the any-host route.