The “PC only” Clash setup—and why phones need a deliberate LAN path
Many households end up with Clash (or any Mihomo-class client) installed on exactly one machine: a Windows desktop or laptop that is always on. Browsers on that PC work because the client exposes a local listener and optionally drives the system proxy. Phones and tablets on the same Wi‑Fi, however, do not magically inherit that configuration. They need an explicit path: your PC’s LAN IP address, a port your core actually binds for HTTP proxy or SOCKS traffic, and—almost always—a firewall rule that lets the rest of the subnet reach that port.
This article is not about Dockerized side gateways or router-level transparent proxying. Those are excellent when you want a dedicated box; we cover them elsewhere. Here the goal is narrower and extremely common: single Windows host, same Wi‑Fi, phones should use the PC as an explicit forward proxy. If you follow the sequence—address, bind, port choice, firewall, then mobile UI—you can reproduce the setup in under twenty minutes and understand why each step exists.
Mental model: what “allow LAN” really does
By default, many clients bind proxy listeners to 127.0.0.1 so only local processes connect. That is the right default for security. Allow LAN (or an explicit bind-address such as * or 0.0.0.0 in YAML) tells the core to accept connections from other devices on your network that can route to the machine. Those devices still send traffic to your PC; the PC’s Clash stack then forwards according to rules, policy groups, and DNS just as it would for local apps.
Phones typically speak HTTP CONNECT for TLS-heavy browsing when you set a “manual proxy” in Wi‑Fi settings. That maps naturally to Clash’s mixed port or a dedicated HTTP port. A raw SOCKS5 port also works if the app or OS lets you choose SOCKS; iOS Wi‑Fi UI historically centers on HTTP/HTTPS proxy fields, so many readers will use the mixed or HTTP listener first. Keep the distinction in mind: typing a SOCKS port into an HTTP-only field produces instant, confusing failure.
Step 1: Find the Windows PC’s IPv4 on the Wi‑Fi adapter
Phones must target the address your PC uses on the same Layer-2 network as the handset. On Wi‑Fi that is almost always a private IPv4 such as 192.168.x.x or 10.x.x.x. Pick the adapter that actually carries internet-bound traffic—usually “Wi‑Fi,” not “vEthernet” from WSL or Hyper-V unless that is where you bridged things on purpose.
Open Windows Terminal or Command Prompt and run:
ipconfig
Under the active Wi‑Fi section, note IPv4 Address, Subnet Mask, and optionally the router Default Gateway. The phone’s address should share the same subnet prefix; if it does not, you are likely on a guest SSID, VPN funnel, or a mesh satellite that isolated clients—more in troubleshooting later.
If you use multiple wireless profiles or Ethernet plus Wi‑Fi, disable the unused interface temporarily while testing so you do not copy the wrong IPv4 into the phone.
Step 2: Enable allow-LAN and identify HTTP vs SOCKS ports
In your GUI (for example Clash Verge Rev), locate the core settings that mirror Mihomo’s YAML: allow-lan or equivalent toggle, and the numeric mixed port, HTTP port, and SOCKS port. Turn allow LAN on before testing from another device. If your client exposes bind address, prefer the pattern that listens on all interfaces when you genuinely want LAN access—your upstream documentation may phrase it as *, 0.0.0.0, or “all interfaces.”
If you are still establishing baseline behavior on the PC itself, walk through our Clash Verge Rev Windows setup guide so system proxy, modes, and subscription imports are settled before you add cross-device complexity.
Write down one port for the phone’s first test. A mixed port is convenient because it accepts both HTTP and SOCKS semantics on the same number; if you split ports, use the HTTP or mixed value in Android and iOS manual proxy fields unless you know the app speaks SOCKS.
Step 3: Windows Defender Firewall—allow inbound TCP to the proxy port
Even with allow-LAN correct, Windows Defender Firewall may silently block inbound TCP to your listener from other hosts. You need a narrow inbound rule: protocol TCP, local port equal to your mixed or HTTP port, scope limited to private subnets if possible.
GUI path: Windows Security → Firewall & network protection → Advanced settings → Inbound Rules → New Rule → Port → TCP → specific local ports → allow the connection → profile selection (Private at minimum for home Wi‑Fi) → name it clearly, e.g., “Clash mixed port 7890 LAN.”
PowerShell (run as Administrator) can create the same rule reproducibly—replace the port with yours:
New-NetFirewallRule -DisplayName "Clash LAN mixed 7890" -Direction Inbound -Protocol TCP -LocalPort 7890 -Action Allow -Profile Private
If you later change the port in Clash, update or duplicate the rule. Stale firewall entries are a frequent cause of “it worked yesterday” confusion.
Step 4: Configure the phone or tablet Wi‑Fi proxy
On Android, open the SSID details → Advanced or Proxy → set Manual → hostname is the PC’s IPv4 → port is your mixed or HTTP port. On iOS/iPadOS, Wi‑Fi ⓘ → Configure Proxy → Manual → Server and Port fields map the same way. Save, toggle airplane mode briefly if the OS caches stale DHCP data, and retest.
Start validation with a simple HTTPS site in the mobile browser. Watch the Mihomo or Clash connections panel on the PC: you should see flows attributed to the phone’s traffic. If nothing appears, the request never reached the listener—return to bind address, firewall, and same-subnet checks before touching rules or nodes.
SOCKS port on the phone: when it applies
Android apps vary: some respect system VPN or proxy settings; many ignore them and use their own stacks. Browser tests remain the honest first signal. If you truly need SOCKS5 for a specific app, confirm the app supports SOCKS and point it at IP:SOCKS_PORT. Mixing that up with the HTTP proxy field produces timeouts that look like “Clash is down” when the core is healthy.
For whole-device coverage on mobile, vendor VPN-style clients (or router-level solutions) differ from “Wi‑Fi manual proxy pointing at a desktop.” If you outgrow per-SSID manual fields, compare this PC-sharing pattern with a dedicated gateway in our Docker side-gateway article—different moving parts, similar end goal.
Security: you are opening a network listener
Any device on the LAN that can route to your PC may attempt to use the proxy once the port is reachable. That includes guests on an open SSID if they share the same broadcast domain. Mitigations are practical: keep guest networks disabled or isolated, prefer Private firewall profiles at home, disable allow-LAN when you do not need it, and avoid exposing the listener to public hotspots.
Authentication between phone and Clash is not TLS-mutual-auth in the typical home YAML; trust is network-bound. Treat coffee-shop Wi‑Fi as incompatible with this pattern unless you also run a proper VPN or router-level segmentation you fully understand.
Troubleshooting: why the phone still cannot connect
- AP / client isolation: Some routers ship “AP isolation,” “WLAN partition,” or a guest SSID that blocks device-to-device traffic. Symptoms include perfect PC browsing and dead phone proxy tests. Fix: join the private LAN SSID or disable isolation in router admin.
- Wrong IPv4: Laptops may prefer Ethernet when docked. Verify
ipconfigagain after sleep or dock changes. - Bind address still loopback: If the core listens only on
127.0.0.1, LAN clients never complete TCP. Re-read allow-LAN and bind settings. - Firewall profile mismatch: A rule tied to “Public” while the Wi‑Fi is categorized as Public can behave differently than expected. Confirm the active profile or temporarily test with a narrowly scoped allow to isolate the issue—then tighten.
- Port drift: GUI updates sometimes reset ports. Confirm the live port in the running config, not an old screenshot.
- DNS on mobile: A working TCP tunnel to the proxy does not guarantee satisfying DNS if rules and fake-ip modes disagree with mobile resolvers. If pages fail only on the phone after TCP succeeds, revisit DNS and rule order using the same log discipline as desktop.
How this differs from transparent gateway setups
This workflow keeps DHCP and default gateways on the phone pointed at the router. The phone explicitly forwards application traffic to the PC proxy port. A transparent or TUN-heavy home gateway, by contrast, intercepts at the IP layer on another box. Each approach has trade-offs: desktop sharing is fast to try and needs no extra hardware; a dedicated gateway scales better for consoles and TVs. Pick based on household topology, not forum fashion.
When you need IP-layer capture on the Windows machine itself—some stubborn binaries ignore both system proxy and manual mobile-style settings—our TUN mode guide explains how that layer differs from explicit HTTP forwarding.
Closing
Sharing Clash from a Windows PC to phones on the same Wi‑Fi is mostly wiring: correct LAN IPv4, a listener that accepts non-local clients, a matching HTTP proxy or SOCKS port choice, and a firewall rule that reflects the same port. Once those align, mobile browsers and compatible apps can ride the same policy groups and rules you already tuned on the desktop—without mystique.
Compared with juggling obscure per-app toggles on phones, a clean desktop-first Mihomo profile plus a controlled LAN share often delivers a steadier day-to-day experience. When you are ready to install or refresh the client from a maintained channel, start from the Clash official home page and keep installers on the documented path.