Mihomo

Quant Proxy Chain: DMIT + IPRoyal + Claude Running Binance quant strategies is always at risk of “IP getting blocked”—suddenly your futures API returns 451 Unavailable. Cloud providers like AWS/GCP have their IP ranges blacklisted by most exchanges, and data center IPs get rate-limited pretty regularly. Here’s the stable proxy chain I built: DMIT Hong Kong VPS as a stable relay + IPRoyal residential IP as the final exit + Claude for monitoring and failover. ...

The previous post covered deploying Xray REALITY on the server side. This one focuses specifically on client configuration—once you’ve collected the usernames, server addresses, public keys and other info for various platforms, here’s how to configure them in different clients. You’ll need to prepare the following information (obtained from the server configuration): Parameter Description Server Address VPS public IP Port Port the server listens on (port 443 recommended) UUID Client ID configured on the server Public Key Public key generated by xray x25519 Short ID One of the shortIds configured on the server SNI serverNames configured on the server (e.g., www.apple.com) mihomo (Clash Meta) mihomo natively supports REALITY. Add the configuration to the proxies: section: ...

Over the past year, I’ve run into a recurring problem with AI tools: airport shared node IPs get flagged by AI platforms, triggering verification requests, feature restrictions, or even account bans. The root cause is simple—these IPs have been used by too many people, and the platform’s risk control system treats them as “abnormal traffic.” The solution: use residential IPs as your exit point. Residential IPs come from real home broadband connections, so to platforms they look like ordinary users—much higher approval rates. ...

AI services like Claude, ChatGPT, and Perplexity are highly sensitive to outbound IP quality. If you route through a standard datacenter VPS proxy, you’ll often hit: Login verification codes Identity re-verification requests Restricted features (Claude Projects, ChatGPT Plus capabilities, etc.) Silent request throttling The reason: these services’ fraud detection identifies IP origins. Datacenter IPs carry the known “proxy traffic” fingerprint; residential IPs don’t. ...

The previous article on multi-gateway home network architecture covered the overall design but didn’t dive into the details of writing rules. This post focuses specifically on Mihomo’s traffic splitting rules, breaking down everything from syntax basics to practical configuration templates. Basic Concepts of Rules Mihomo controls traffic splitting through the rules field. Each rule follows this format: rule-type,match-value,proxy-group For example: rules: - DOMAIN-SUFFIX,google.com,Proxy - IP-CIDR,192.168.0.0/16,DIRECT - GEOIP,CN,DIRECT - MATCH,Proxy # fallback rule — matches all remaining traffic Rules are matched in order — the first rule that matches is executed, and subsequent rules are skipped. Order is critical. ...

Hysteria2 is a proxy tool based on the QUIC protocol (UDP) that significantly outperforms TCP in high-loss and high-latency networks. It complements VLESS+XTLS-Reality: use Hysteria2 when TCP is throttled, and VLESS+Reality when UDP is blocked—deploying both protocols together is currently the most stable approach. Why Choose Hysteria2 Core advantages: QUIC/UDP-based, maintains good speed even in high-loss networks Built-in bandwidth obfuscation makes traffic patterns harder to identify precisely Simple configuration, lighter weight than Xray Native support in mihomo (Clash Meta) Use cases: ...

After half a year of tinkering with my home network, I finally got a multi-gateway redundancy architecture working. This article shares the overall design approach—it’s for people with some hands-on experience who want a more stable network. Why You Need Multiple Gateways The biggest problem with a single gateway is a single point of failure: if your VPS gets blocked, the line stutters, or the machine crashes, your entire network goes down. ...