Routing rules

HypoMux can route by process, domain and subdomain, or destination IP / CIDR. Each rule can use aggregation, direct access, Ethernet, Wi-Fi, or a specific adapter.

Rules are managed from the Routing Rules page. New and edited rules normally affect connections made afterward, so reconnect the affected app or restart it when necessary.

Screenshot pending

Routing Rules pageShow process, domain, and IP/CIDR tabs alongside the outbound selector. Use example.com and 192.0.2.0/24 instead of real targets.Upload to public/docs/routing-rule-list.png

Add a rule

1. Select a match type: process, domain, or IP / CIDR.
2. Enter the value: an executable filename, domain, or IP address/network.
3. Choose an outbound: multi-network aggregation, direct, or a specific adapter.
4. Save, then establish a new connection and verify the result.

For example, route steam.exe to aggregation for concurrent game updates, while routing a game or meeting app directly to preserve its original latency path.

Ask AI to help design rules

If you are unsure which apps should aggregate or route directly, you can ask your preferred AI assistant to analyze your use case. Treat its answer as a draft: review every rule, add it in HypoMux, and verify it with new connections.

What to tell the AI

• The apps or services that need network access, such as download managers, launchers, games, and meeting apps.
• Your goal: higher download throughput, lower game latency, or pinning a service to one adapter.
• Connected adapters and their roles, for example “Ethernet is stable; mobile data is limited.”
• Whether a VPN, TUN, local proxy, or accelerator is running.
• The output format you need: an importable HypoMux JSON rule file.

Copy this prompt

I use HypoMux on Windows and want help designing routing rules.

My network and requirements:
- Connected adapters: {for example: Ethernet, Wi-Fi, mobile hotspot}
- Main goal: {for example: aggregate Steam downloads while keeping games and voice low latency}
- Apps or services to handle: {for example: steam.exe, game executable, Discord}
- VPN, TUN, proxy, or accelerator currently in use: {write “none” if not applicable}

Generate importable HypoMux JSON from only this information. Do not return Markdown, an explanation, or anything outside the JSON code block.
Use this exact format. Only use aggregation (multi-network aggregation) or direct as the outbound policy.

{
  "format": "hypomux-routing-rules",
  "version": 2,
  "rules": [
    { "match_type": "process", "value": "example.exe", "outbound": "aggregation" }
  ]
}

Do not suggest bypassing access controls on any website, service, or network. Mark uncertain process names, domains, or IPs as “needs confirmation”.

Save and import the JSON

1. Save the AI response as a UTF-8 .json file, for example hypomux-routing-rules.json.
2. In HypoMux Routing Rules, select Export backup first and keep the current rules safe.
3. Select Import backup, choose the JSON file, review its preview, and confirm the import.

Importing replaces the current rules with the rules in the file, so keep the exported backup. AI does not know the internal adapter ID on your computer; if you need a specific adapter, select it manually in HypoMux after import.

Example

“I have Ethernet and Wi-Fi. I want Steam updates to download as quickly as possible, but game.exe, Discord, and meeting apps should keep low latency. I do not use a VPN or another TUN. Return importable JSON in HypoMux hypomux-routing-rules v2 format and use only aggregation and direct outbounds.”

Review before use

Do not share account details, passwords, access tokens, full public IPs, raw logs, or other sensitive data with an AI assistant. AI cannot see your live network environment and does not replace Network Check, connection verification, or your final review.

Recommended policy

• Use aggregation for download managers, game launchers, and large browser downloads.
• Use direct routing for competitive games, voice, and video meetings.
• Record a domain as restricted on an adapter if that path cannot reach it, so later connections are not assigned to the same path.

Third-party proxies and accelerators

HypoMux attempts to identify common local proxies and game accelerators and establishes direct bypasses to reduce proxy loops. Keep these boundaries in mind:

1. Do not let two programs take over the Windows system-proxy switch at the same time.
2. If another program's TUN / VPN has taken the default route, stop it before starting HypoMux Virtual Adapter mode.
3. After third-party tool updates, check compatibility notices and support logs before changing modes.

WARNING

Rules do not bypass access controls set by websites, services, or networks. Use them only on devices and networks you own or are authorized to use, and comply with the relevant service rules.