1. Scope: why international students need two network paths
International students living in China often discover that “the internet” is not one consistent environment. Your university portal, course registration system, dormitory authentication page, library resources, local payment apps, and Chinese streaming services may work best through the campus or domestic network. At the same time, Google Workspace, GitHub, Microsoft services, research databases, cloud documentation, messaging platforms, and services hosted outside China may require a different route. Switching a VPN on and off is possible, but it quickly becomes frustrating when a browser contains both domestic and international tabs, or when a laptop runs several applications with different proxy behavior.
This article explains how to use Clash, especially Clash Verge Rev or another Mihomo-compatible client, to create a practical split-routing setup for study and daily life. The objective is not to send every connection through one remote server. Instead, you will keep university and China-based services on DIRECT where appropriate, while sending selected international traffic through a reliable proxy group. That arrangement usually reduces latency for local services, avoids unnecessary load on your proxy subscription, and makes failures easier to diagnose.
The exact domains used by a university vary. Some schools place their learning management system behind a domestic cloud provider; others use Google Workspace, Microsoft 365, Canvas, Moodle, or a custom identity provider. Treat the rules in this guide as a starting framework rather than a permanent domain list. Confirm each important hostname from your own browser’s network logs, your school’s official documentation, and the policies that apply to your campus account.
Do not route sensitive academic records, payment details, identity documents, or research data through an unknown proxy operator. A working connection is not proof that the relay is trustworthy.
2. Decide what should be DIRECT and what should use a proxy
A useful student profile begins with a traffic inventory. Write down the services you use during a normal week and classify them by purpose, location, and sensitivity. This is more reliable than copying a large “China rules” list from a forum, because university networks can use unusual subdomains, regional redirects, and single sign-on providers that generic lists do not know about.
| Traffic category | Typical examples | Initial routing idea | Reason |
|---|---|---|---|
| Campus access | Wi-Fi login, dorm portal, intranet, library gateway | DIRECT | Local access, lower latency, campus authentication compatibility |
| Chinese daily services | Banking, Alipay, WeChat, local shopping, domestic media | DIRECT or China group | Domestic endpoints may reject foreign exits or trigger security checks |
| International study tools | GitHub, Google services, overseas research platforms, package registries | Proxy group | More predictable access through an appropriate international relay |
| Video meetings | Zoom, Teams, university conferencing, Webex | Test individually | Real-time traffic is sensitive to latency, UDP support, and regional policy |
| Private or regulated data | Student records, payment pages, identity verification | Official route only | Minimize exposure and follow institutional requirements |
Start with broad categories, but do not assume that every domain under a familiar brand has the same routing requirement. A university portal may redirect authentication to a third-party identity provider. A research website may load its main page from one country and download PDF files from a separate content delivery network. If the first page opens but a login loop or download fails, the missing hostname is often visible in the browser’s Developer Tools rather than in the address bar.
There is also a difference between a domain being reachable and a service being usable. A banking application may open through a proxy but refuse a login because the exit location looks unusual. A school system may load its dashboard through a proxy but block a file upload because the session changes source characteristics. For these services, a direct domestic route is usually preferable when it is available and allowed.
3. Prepare Clash for dorm and campus networks
Before writing rules, confirm that Clash itself can reach both kinds of traffic. Connect to the dorm or campus network and complete any captive portal process in a normal browser. Many networks require a web-based acceptance page, a student number, or device registration before general access is enabled. If the portal cannot open while the system proxy or TUN mode is active, temporarily disable the feature, authenticate, and then enable Clash again. Do not assume that a proxy client can solve a network access-control page that has not yet authorized your device.
Import your Mihomo-compatible profile into Clash Verge Rev and verify that the proxy groups contain working nodes. Select a low-latency node near your current region rather than automatically choosing the most distant “premium” label. Test with several ordinary sites and observe the delay, packet loss, and stability over at least a few minutes. A node that looks fast on a single speed test may perform poorly with long-lived academic downloads, video calls, or repeated TLS connections.
Use a clear group structure. Names differ between subscriptions, so adjust the references to match your actual profile. The following example shows the logic rather than a complete production configuration:
mixed-port: 7890
mode: rule
allow-lan: false
log-level: info
dns:
enable: true
ipv6: false
enhanced-mode: fake-ip
nameserver:
- https://1.1.1.1/dns-query
- https://dns.google/dns-query
rules:
- DOMAIN-SUFFIX,university.example.edu,DIRECT
- DOMAIN-SUFFIX,campus.example.cn,DIRECT
- DOMAIN-SUFFIX,library.example.cn,DIRECT
- DOMAIN-SUFFIX,github.com,Study-Proxy
- DOMAIN-SUFFIX,githubusercontent.com,Study-Proxy
- DOMAIN-SUFFIX,google.com,Study-Proxy
- DOMAIN-SUFFIX,googleapis.com,Study-Proxy
- DOMAIN-SUFFIX,edu.cn,DIRECT
- GEOIP,CN,DIRECT
- MATCH,Study-Proxy
The example intentionally places specific rules before the general GEOIP,CN,DIRECT line. Mihomo evaluates rules from top to bottom, so an international service hosted on a Chinese IP range could otherwise be sent direct before the more precise rule is considered. Likewise, a broad proxy rule placed too early can capture campus services and create unnecessary login problems.
Do not enable allow-lan: true simply because a tutorial uses it. On a dormitory network, allowing other devices to use your Clash port can expose a proxy endpoint to nearby users. If you need to share a connection with your own tablet or phone, restrict the bind address and firewall access carefully, and understand that the campus network may treat traffic from multiple devices differently.
4. Build and test rules with real browser traffic
The most dependable workflow is incremental. Begin with a small group of high-confidence domains, test the service, and add only the hostnames that appear in a failure. In Clash Verge Rev, open the connections or logs panel while reproducing one task at a time. For example, open the university learning portal, sign in, download one lecture file, and submit a harmless test document if the course system provides a safe test area. Then repeat the process for GitHub, a research database, and the cloud tools used by your department.
Observe the connection log before adding rules
When a page fails, record the destination domain, the selected rule, the proxy group, and the result. A single page can contact dozens of domains for fonts, JavaScript bundles, authentication, analytics, document storage, and embedded media. Do not add every hostname automatically. First determine whether it is essential, whether it carries private information, and whether its route should match the main service.
A practical naming scheme makes later maintenance easier. Separate groups for Study-Proxy, China-Direct, and Video-Test are more understandable than a single group named “Proxy.” If your subscription supplies an automatic selection group, use that as a member of Study-Proxy, but keep a manual fallback available. Automatic health checks can select a node that responds quickly to a test URL while performing badly for the actual service you need.
Use domain rules before geographic fallbacks
A common pattern is to place known campus domains first, followed by selected international domains, then a geographic fallback, and finally a catch-all policy. In simplified form:
rules:
- DOMAIN-SUFFIX,portal.your-university.edu,DIRECT
- DOMAIN-SUFFIX,login.your-university.edu,DIRECT
- DOMAIN-SUFFIX,github.com,Study-Proxy
- DOMAIN-SUFFIX,raw.githubusercontent.com,Study-Proxy
- DOMAIN-SUFFIX,accounts.google.com,Study-Proxy
- DOMAIN-SUFFIX,docs.google.com,Study-Proxy
- DOMAIN-SUFFIX,bank.example.cn,DIRECT
- GEOSITE,CN,DIRECT
- MATCH,Study-Proxy
Use DOMAIN when you mean one exact hostname and DOMAIN-SUFFIX when subdomains are part of the service. Avoid overly broad suffixes. A rule for google.com may be reasonable in a personal study profile, but a rule for a generic cloud provider suffix could unintentionally proxy unrelated university systems. For large services, review the connection log after each update because login and storage endpoints can change.
After editing a profile, reload it and clear only the relevant browser state if necessary. Do not clear all cookies immediately: that can erase useful evidence about whether the failure is caused by routing, authentication, or an expired session. Test DNS separately from HTTPS. If a hostname resolves but the connection times out, the problem may be the selected route. If it resolves to an unexpected address under fake-IP mode, compare behavior with the profile’s DNS settings and consider whether that service needs a compatible fake-IP filter or redirection strategy.
5. Tune the setup for laptops, phones, and research tools
Laptops are usually the easiest starting point because Clash Verge Rev can manage system proxy settings and, when supported by the operating system, TUN mode. System proxy mode is often sufficient for browsers and applications that respect operating-system settings. TUN mode captures more traffic, including applications that ignore HTTP proxy variables, but it also increases the importance of DNS behavior, permission prompts, and rule ordering. Enable it only after the basic browser workflow works, and keep a way to disable it when the campus login page or a local device service stops responding.
On Windows, remember that an IDE, terminal, and browser may each retain different proxy state. Restart a terminal or IDE after changing environment variables. On macOS, check whether the application uses the system proxy or opens its own network stack. On Linux, command-line tools may require explicit variables:
export HTTP_PROXY=http://127.0.0.1:7890
export HTTPS_PROXY=http://127.0.0.1:7890
export ALL_PROXY=socks5://127.0.0.1:7891
curl -I https://github.com
git config --global http.proxy http://127.0.0.1:7890
Do not set Git’s global proxy permanently without understanding the consequence. A university Git server or a local laboratory repository may need a direct connection. Prefer host-specific configuration when your workflow mixes domestic and international remotes, and remove credentials from any command output before sharing diagnostics.
Phones require additional caution. Android applications vary widely in proxy support, and some banking or campus apps may detect VPN or TUN behavior. Use Clash for Android or a compatible Mihomo client only where permitted, keep sensitive domestic applications on the route recommended by their provider, and avoid installing configuration files from untrusted sources. If the phone is used for two-factor authentication, stability and account safety matter more than forcing every app through the same policy.
For study services, measure usability rather than only speed. Check whether a library PDF completes, whether a Git clone resumes correctly, whether a video lecture remains stable for twenty minutes, and whether an academic login survives a redirect. Record the date, network, selected node, and rule that was used. Dorm networks can change during busy hours, and a profile that works at midnight may need a different node or fallback during an evening lecture.
6. Common failures and a maintainable Clash profile
If campus pages fail after enabling Clash, first test DIRECT for the exact portal and identity-provider domains. Captive portals often depend on local redirects, nonstandard ports, or DNS responses that do not behave well through a remote resolver. If international pages load but sign-in loops, inspect every redirect hostname instead of routing only the visible service domain. If downloads fail while pages work, look for a separate storage or content-delivery hostname in the connection log.
DNS mistakes are another frequent source of confusing results. Fake-IP mode can improve consistency for rule-based routing, but some software expects a real address, performs its own DNS queries, or uses certificate and IP checks that conflict with synthetic responses. Do not change several DNS options at once. Make one change, reload the profile, reproduce the same request, and compare the logs. This controlled approach is slower than copying a “magic” DNS block, but it leaves you with an explanation you can reuse.
Keep comments in your configuration or maintain a separate change log. Note why a hostname was added, which service required it, and whether it should be direct or proxied. Review the profile every semester: remove old dorm portals, temporary research tools, and duplicated rules; confirm that subscription nodes still work; and test the fallback route before traveling. A small, understandable ruleset is easier to repair than a huge list containing hundreds of unverified domains.
Finally, separate technical diagnosis from policy decisions. Clash can choose a route, but it cannot determine whether a service is available to your account, whether a university permits a particular connection method, or whether a proxy provider handles your data responsibly. Follow campus IT guidance, local law, service terms, and your department’s research-security requirements. For sensitive work, use official institutional access methods such as the university VPN, library proxy, or approved remote desktop instead of improvising with a personal relay.
Compared with simple VPN toggles or app-specific proxy tools, which often force you to choose between slow access to local services and unreliable access to international study platforms, Clash gives you observable rules, per-domain decisions, fallback groups, and a consistent configuration across supported devices. When those controls are combined with a small, evidence-based hostname list and careful handling of academic and payment data, daily work becomes less disruptive: campus systems can remain direct, while GitHub, Google tools, and other approved international resources use a tested study route. If that is the balance you need, you can choose a compatible client and begin with a minimal profile rather than changing your entire network at once.
Ready to get started?
Set up a dependable split-routing workflow for campus access, study tools, and everyday services.