MIHOMO CORE · RULE ROUTING
Built around the mihomo core, this collection covers Windows, macOS, Android, iOS, and Linux clients, with practical configuration paths for subscription imports, rule-based routing, and network diagnostics.
TEST BENCH / ROUTING
The sections below follow one connection from entry through the local port to its selected exit. Switch between test cases to see what rules, DNS, TUN, and subscription settings handle, and which results to check during configuration.
Rule mode checks domains, IPs, processes, and dedicated rule sets from top to bottom; the first match determines whether a connection is direct, proxied, or rejected. Put narrow, explicit rules first, and keep MATCH at the end alongside other broad rules. Unlike clients that offer only a global switch, mihomo can handle LAN traffic, work systems, media services, and ordinary web pages separately. Connection logs also show the exact matching rule during troubleshooting, rather than relying only on whether a page opens.
The DNS module can assign separate default and proxy-side resolvers and domain policies, connecting system requests through fake-ip or redir-host mode. The key is not adding more addresses, but confirming which interface sends each request, whether rule matching needs the real IP or a mapped address, and whether LAN domains should be excluded. mihomo can assign a dedicated nameserver to selected domains, keeping resolution aligned with the access route and reducing failures caused by mismatched DNS results and connection paths.
TUN mode receives system traffic through a virtual network interface, making it useful for command-line tools, certain applications, and games that ignore system proxy settings. Before enabling it, check OS permissions, automatic route configuration, DNS interception scope, and LAN exclusions. Afterward, reconnect and verify the default route and LAN access. TUN is not simply a stronger system proxy: browsers usually work well with the system proxy first, while TUN is best added when coverage is insufficient for a clearer troubleshooting path.
Subscriptions usually provide nodes and proxy groups, while rule providers supply independently updateable match sets. After importing, verify that the configuration parses, then confirm that referenced node names and rule providers have loaded. When updates fail, check link reachability, response format, field compatibility, and proxy loops in that order; this is more effective than repeatedly deleting and re-importing. mihomo keeps node sources and rule sources separate, so routine updates do not require frequent edits to the main configuration.
Windows, macOS, Android, iOS, and Linux clients differ in interface entry points, system services, and permission models, but their core tasks remain loading configuration, selecting policies, taking over traffic, and displaying connection logs. Desktop clients suit persistent tray operation and configuration editing; mobile clients depend on system VPN permissions and background behavior; Linux can also run the core directly. Choose based on platform maintenance and required features first, then consider interface preferences rather than judging by similar names alone.
PLATFORM ACCESS
The download page lists available graphical clients, system requirements, and installation links by platform. It does not distribute installers directly; platform links open the relevant category so you can compare clients on the same system.
P-01 / DESKTOP
Suitable for desktop environments that need a persistent tray client, system proxy switching, and TUN takeover. The download page also lists Clash Plus, Clash Verge Rev, FlClash, Clash Nyanpasu, and archived clients, making it easier to choose by maintenance status and interface preferences. After installation, import a subscription and confirm the system proxy switch and listening port.
Go to downloadsP-02 / DESKTOP
Suitable for Apple Silicon and Intel Macs. Check the processor architecture before installation, then follow the system prompts to authorize the network extension or helper service on first launch. For browser traffic alone, start with the system proxy; enable TUN only when needed for terminal tools and other applications that ignore proxy settings.
Go to downloadsP-03 / MOBILE
Android clients take over app connections through the system VPN interface and require explicit connection permission after configuration import. Background restrictions vary by device. If the connection drops after the screen locks, check battery policy, background activity permission, and VPN status before changing nodes or rules.
Go to downloadsP-04 / MOBILE
iPhone and iPad use a system network extension to establish the proxy connection. Configuration focuses on importing a subscription, choosing proxy groups, and authorizing the system VPN. After connecting, check the client log to verify domain matches. The download page links to Clash Plus in the App Store and its official site at clashplus.io for product details.
Go to downloadsP-05 / DESKTOP
Desktop users can choose a graphical client, while servers, software routers, and container environments are better suited to running the mihomo core directly. Before configuring, define the service user, configuration directory, and startup method, then hand logs to the system service manager. Graphical clients and core packages serve different purposes; for ordinary desktops, choose the former.
Go to downloadsTHREE-STAGE SETUP
A first setup does not require changing every advanced option at once. Establish a repeatable baseline: confirm that the client parses the subscription, choose rule mode and proxy groups, then verify matches in the connection log. Once the basic path is stable, move on to TUN, DNS, or custom rules.
This order limits each problem to one stage. If import already fails, there is no need to inspect the system proxy; if configuration loads but an application has no traffic, check permissions, ports, and the takeover method instead. The full guide covers interface entry points and common status messages.
View the complete guide →Add the service provider's link on the client's configuration or subscription page, update it, and check for proxy groups, nodes, and rules. If the configuration is blank or parsing fails, first confirm that the link returns content supported by the client; do not enable the system proxy yet.
Rule mode is usually best for daily use, followed by selecting an available policy in the main proxy group. Global mode sends most connections through the current policy, while direct mode bypasses the proxy; both are better suited to temporary tests. Reconnect active sessions after switching.
Enable the system proxy first and open a test page. Check whether a new entry appears in the client connection list and whether its rule matches expectations. If the target program ignores the system proxy, evaluate TUN next. Verify web access, LAN devices, and frequently used applications together rather than judging from one page.
OPEN SOURCE RECORD
Project relationship.Clash Meta commonly refers to the feature ecosystem formed around the Meta branch, while the core project is now developed under the mihomo name. Graphical clients handle configuration management, system services, tray interaction, and log display; the mihomo core handles protocols, rule matching, DNS, and inbound and outbound connections. Understanding this relationship helps identify whether an issue occurs in the interface, system permissions, configuration file, or core runtime.
Open collaboration.mihomo source code, commit history, issue discussions, and release notes are maintained in public repositories. Users can track implementation changes to configuration fields, and client maintainers can build frontends for different platforms on the same core. This site bases its Chinese documentation on public materials and observed configuration behavior; it does not treat a UI label as a core capability or merge differences between third-party clients into one conclusion.
Update paths.The core, graphical client, subscription content, and rule sets follow four separate update paths. Client updates may change the interface and system services; core updates may alter configuration fields or network behavior; subscription updates mainly affect nodes and policies; rule-set updates change the range of matching connections. During troubleshooting, record which layer changed most recently and restore a single variable first instead of updating everything at once.
Documentation principles.Configuration notes prioritize observable results: whether the file loads, whether the port is listening, whether the system proxy points to the correct address, which rule matched, and which resolver handled the DNS request. Permissions and network stacks differ across operating systems, so the same switch may have different prerequisites. Where platforms differ, the guide lists separate steps rather than summarizing every environment with one screenshot.
SOURCE COMMAND
The command below clones the public repository for users who want to inspect configuration behavior, follow issues, or contribute. Ordinary client installation does not require it.
git clone https://github.com/MetaCubeX/mihomo.git
OBS-01
Confirm that YAML parses, external rule sets are readable, and referenced policy-group names match. Before traffic takeover begins, parsing failures should be addressed through indentation, field compatibility, or remote-content reachability.
OBS-02
The system proxy works for programs that follow proxy settings, while TUN covers a broader range of network traffic. Both involve system permissions and routing; reconnect after switching and check LAN access.
OBS-03
A successful connection does not prove that routing is correct. Check the target domain, final IP, matching rule, and selected policy to distinguish an unavailable proxy, incorrect rule order, and abnormal DNS results.
OBS-04
Change one category at a time and keep the last working configuration. If something breaks, you can roll back quickly and identify whether the change came from rules, DNS, subscriptions, or client settings.
SHORT ANSWERS
These questions help define a troubleshooting direction. For configuration-field meanings, continue to the glossary; for complete procedures, open the user guide.
Clash Meta is a widely used name for this branch and its ecosystem, while the core project is currently maintained under the mihomo name. Different graphical clients can call the mihomo core, but each project controls its own interface, system services, and release schedule. See the glossary's core and architecture section for more details.
Rule mode is generally best for daily configuration, sending connections to different policies based on domains, IPs, and rule sets. Global mode helps temporarily confirm whether a proxy policy works, while direct mode helps rule out proxy-related factors. Existing connections may keep their previous route after a switch, so close the target app's connections and test again.
Some apps do not read system proxy settings and may implement their own network stack. First confirm that browser traffic reaches the client, then check whether the target app supports proxy settings. If broader coverage is required, enable TUN and verify administrator permission, the virtual adapter, routes, and DNS takeover status.
First check whether the subscription URL is reachable and still returns valid configuration, then review the client's HTTP status, parsing messages, and field errors. If manual access works but the client update fails, check whether the current proxy rules create a loop for the update request. See the subscription update troubleshooting notes for detailed steps.
FIELD NOTES
Articles are organized around specific problems, recording trigger conditions, check order, and post-change verification. Dates mark when the content was compiled; before configuring, compare fields with the current client interface and core documentation.
Check link expiration, blocked requests, proxy loops, and format changes in that order. The article also explains where to set the automatic update interval and which status to watch after forcing a manual update.
Read the full articleExplains how the three modes differ by connection flow, with guidance for daily browsing, temporary testing, and intranet troubleshooting, plus why connections must be re-established after switching.
Read the full articleCovers subscription entry points in different clients, explains the differences between standard YAML, Base64, and universal share links, and shows how to confirm that nodes, proxy groups, and rules loaded after import.
Read the full article