TUN mode in Mihomo Party gives the Mihomo core a virtual network interface through which it can capture traffic from Windows applications. This is useful when a program ignores the Windows system proxy, does not support proxy settings, or needs traffic routed consistently without configuring each application separately. TUN is not simply a second system-proxy switch: it changes how traffic enters the core and may affect more of the computer’s network connections.
Before enabling it, confirm that your Mihomo Party installation starts normally and that the active profile can connect using the ordinary system proxy. Keep a copy of any custom configuration or overrides, and note how to turn TUN off again. The exact labels and available options vary by Mihomo Party version and bundled Mihomo core, so treat the names below as guidance rather than assuming every build has an identical layout.
Mihomo Party TUN Mode Setup on Windows: Enable It Safely
Understand what TUN changes
With the Windows system proxy enabled, Windows applications that follow the operating system’s proxy settings send requests to a local HTTP or SOCKS proxy port. Applications that connect directly may bypass that path. TUN mode creates or uses a virtual network adapter and routes selected traffic through it, allowing Mihomo to process traffic that does not use the system proxy setting.
This broader capture can make TUN useful for command-line tools, games, development software, and applications with their own networking stacks. It also means that a TUN configuration problem can affect more than one browser or program. If the profile has incorrect rules, DNS settings, or proxy-group selections, those issues can become visible across applications that previously connected directly.
- System proxy: usually affects applications that read the Windows proxy setting. It is easy to inspect and is often sufficient for browsers and common desktop software.
- TUN mode: captures traffic through a virtual adapter and can cover applications that bypass the system proxy. It requires more network integration and may need elevated permissions.
- Running both: can be appropriate when the client manages the combination, but manually configuring multiple proxy paths can make troubleshooting harder. Begin with one known-good path.
TUN does not create a proxy service or supply working nodes by itself. The active profile still needs usable proxies, valid groups, and rules that direct traffic to the intended policy. A successful TUN startup only confirms that the virtual interface and core have started; it does not prove that every destination is routed correctly.
Prepare Windows and the active profile
Start Mihomo Party and confirm that the selected profile is loaded without errors. Check that a proxy group contains at least one usable choice, select an appropriate policy, and make a basic connection test using system proxy mode if available. If the core cannot start or the profile fails validation, resolve that issue before introducing TUN; otherwise, a network failure may be difficult to attribute to one cause.
Close other proxy clients while testing. Two clients can compete to change the Windows proxy setting, install or control virtual adapters, or bind the same local ports. If another VPN or network-filtering application is essential, do not uninstall it immediately, but note that it may conflict with route management or DNS interception. Test with one network-routing tool active at a time where practical.
Use a Windows account that can approve administrator prompts. TUN setup may need permission to create or configure a virtual network adapter and routes. Depending on the client version and installation, Mihomo Party may request elevation when you enable the feature, or it may offer a service or helper-based permission mechanism. Approve only the expected prompt initiated by the client you installed. If elevation is denied, do not try to compensate by manually changing protected Windows routes.
It is also useful to record the current network state before changing it. Open PowerShell and save the output of these commands somewhere accessible:
Get-NetAdapter
Get-NetIPConfiguration
route print
These commands are for inspection. They show network adapters, IP configuration, and the route table; they do not enable TUN or modify Windows networking. If a problem occurs, comparing the output before and after activation can help identify whether the virtual adapter appeared and whether routes changed as expected.
Enable TUN in Mihomo Party
Open Mihomo Party’s settings and look for the Mihomo, core, or network settings area. In many builds, the control is labelled TUN, TUN Mode, or a similar term. If the setting is not visible, check whether the application or core is up to date and whether the selected core supports TUN. The client interface and bundled core are separate components, so a visible client toggle does not guarantee that every core build exposes the same options.
- Make sure the intended profile is active and the core is running.
- Open the TUN settings and review any available options before switching the feature on.
- If the client asks for administrator permission or offers to install its network helper, follow the prompt shown by the application. If Windows asks for confirmation, verify that it corresponds to your action.
- Enable TUN and wait for the client to report that the core is running. If it reports an error, record the message before restarting or changing other settings.
- Open the connection list or log and generate a fresh request from a test application. Confirm that the request appears and is matched to the expected rule or policy group.
Some versions expose advanced TUN options. Names and defaults may vary, but the following concepts are common in Mihomo configurations:
auto-routecontrols whether routes are added to direct traffic into the TUN interface. When exposed as a client option, leave the default enabled unless you have a specific routing design.strict-routeapplies stricter route handling on supported platforms. It can help prevent traffic from escaping through an unintended path, but it may also affect local-network access. Do not enable it solely because the name sounds safer; use the client’s guidance and test local resources afterward.dns-hijackrelates to handling DNS requests through the core. DNS behavior depends on the profile and core version. Avoid adding custom interception addresses unless you understand how the active DNS configuration uses them.- A TUN stack option, if present, selects how the core processes traffic. Keep the client’s default initially. Change it only to address a specific compatibility issue and compare behavior after each change.
Do not paste a generic TUN YAML block into a subscription-generated profile without checking how Mihomo Party manages configuration. The client may build runtime settings from the profile and its own overrides, and a later update may replace direct edits. If you need a persistent change, use the client’s supported override or configuration editor and validate the resulting configuration before applying it.
Verify the adapter and test applications
After TUN starts, check Windows for a new or active virtual network adapter. The exact adapter name can differ by installation and core implementation. In PowerShell, run:
Get-NetAdapter | Format-Table Name, Status, InterfaceDescription -AutoSize
Look for an adapter associated with the TUN implementation and check whether its status is active. Its name may contain a product or driver label, but do not rely on a particular name as a universal requirement. If no relevant adapter appears, check Mihomo Party’s startup log and permission status before attempting a reinstall.
Test gradually rather than opening several applications at once. First load a page in a browser with browser-specific proxy extensions disabled, then try an application that normally ignores the system proxy, such as a command-line tool that connects directly. In Mihomo Party, confirm that each fresh connection appears in the connection view and inspect the matched rule and policy. If the application works but no connection is visible, it may be using another network path, a cached connection, or a separate VPN.
For a basic DNS and connectivity check, PowerShell can run:
Resolve-DnsName example.com
Test-NetConnection example.com -Port 443
These tests help distinguish name resolution from a TCP connection failure, but they do not by themselves prove that traffic used the intended proxy. Use them together with Mihomo Party’s connection log. Test a destination appropriate for your profile, and remember that different domains or ports may match different rules.
Also test local resources you normally use, such as a printer, NAS, or a router’s local management page. TUN route settings can change how local traffic is handled. If a local device becomes unreachable after TUN is enabled, note whether its address is on a private LAN range and review the client’s route or LAN-access options. Do not add a broad bypass rule until you have confirmed which destination needs to remain direct.
Troubleshoot TUN startup and traffic
If TUN will not start, begin with the exact error in Mihomo Party’s log or notification. A message about permissions suggests that the elevation or helper step did not complete. A missing-adapter or driver-related message points toward the virtual network component. A core startup error may instead indicate an unsupported option, a malformed profile, or a core problem. These cases need different fixes, so avoid treating every TUN failure as a Windows firewall issue.
- Permission prompt was declined: turn TUN off, restart Mihomo Party, and enable it again while approving the expected request. If the client provides a documented helper or service setup, use that interface rather than manually changing service permissions.
- The adapter does not appear: check the client log, confirm that the core supports TUN, and restart the client once. If the error names a missing component, use the installation or repair method supplied for that Mihomo Party build.
- TUN starts but applications have no access: confirm that the profile and proxy group work, inspect the connection log, and test DNS separately from TCP connectivity. A started adapter cannot compensate for an unavailable proxy node or a rule that sends traffic to the wrong policy.
- Only some applications fail: check their own VPN, proxy, DNS, or network settings and test a new connection after closing and reopening the application. Some programs retain existing sockets or use specialized networking behavior.
- Local devices stop working: temporarily disable TUN to confirm the relationship, then review the client’s LAN and routing options. Restore local access with a narrow, understood rule rather than disabling route protection globally.
- Connectivity changes after sleep or network switching: turn TUN off and on from the client, then check the adapter and logs. Wi-Fi changes, VPN reconnections, and interface priority changes can leave the active route different from the one used during initial startup.
If ordinary browsing fails immediately after TUN is enabled, switch TUN off from Mihomo Party and confirm that Windows connectivity returns. Then compare the adapter and route output with the notes you saved earlier. Restarting the client may be reasonable after recording the error, but repeatedly toggling TUN without checking logs can obscure the original failure. If the problem persists, collect the Mihomo Party version, core version, Windows version, relevant error text, and whether the virtual adapter appeared; remove account credentials and subscription URLs before sharing logs.
Once tests pass, keep the default options that work and change advanced routing settings only for a specific need. If TUN is unnecessary for your applications, the system proxy remains a simpler option. If you need broad application coverage, use TUN deliberately, verify the route after network changes, and keep a clear way to disable it during troubleshooting.
Choose a client and continue setup
For a fresh installation, confirm that you have selected a Windows build compatible with your system and review the client’s setup instructions before enabling network-level features. Keep the active profile backed up and make changes incrementally so that a profile issue, permission issue, and adapter issue can be distinguished.