Sharing Clash at home can mean several different things: installing a client on every device, letting other devices use one computer’s LAN proxy, or running a proxy core on the router. These approaches can all work, but they differ in which traffic they capture, how much configuration they require, and what happens when the host device is turned off.
Start by deciding what “share” needs to mean in your household. If only a laptop and a phone need occasional proxy access, a LAN proxy on a computer may be enough. If televisions, game consoles, and devices without proxy settings must also use selected routes, a router-based setup may be more suitable. Installing a client on each device gives each one independent control, but it also means maintaining more configurations and checking more system settings.
In every design, keep the proxy core, the client interface, and the home network in view. A GUI client such as Clash Verge Rev can start Mihomo and manage its settings, while the router or another device provides the network address that clients connect to. A working proxy on one computer does not automatically make it available to the rest of the LAN.
Share Clash Across Your Home: Router and Multi-Device Setup
Choose a sharing model before changing settings
There are three common ways to use Clash across a home network. Choose based on the devices involved and the level of control you need, rather than assuming that one approach is best for every household.
- Install a client on each device. Each computer or phone runs its own compatible client and uses its own local connection. This is usually the simplest model for devices with supported apps. Each device can select a different policy group, but configuration updates, permissions, and troubleshooting happen separately.
- Share a LAN proxy from a computer. One computer runs Clash or Mihomo, listens on a LAN-accessible address, and accepts proxy requests from other devices. This is practical for occasional use and does not require replacing router firmware. The host must remain awake and connected to the same network, and client applications must support the proxy protocol or operating-system proxy settings.
- Run the proxy on a router or dedicated gateway. The router or a separate always-on device runs a compatible core and routes traffic for some or all LAN clients. This can simplify household-wide management, but it requires supported hardware, careful firewall and routing configuration, and a way to recover the router if a change interrupts access.
These models do not provide identical coverage. A LAN HTTP or SOCKS proxy only handles requests that explicitly connect to it. It does not transparently intercept every packet from a phone or television. A router setup may use transparent routing or a TUN-style interface, depending on its operating system and implementation, but those mechanisms are not interchangeable with simply opening a proxy port.
Also consider availability. A computer-hosted proxy stops working when that computer sleeps, changes networks, or shuts down. A router or dedicated gateway is more likely to stay online, but it becomes a central dependency: a bad update or routing rule can affect several household devices at once.
Understand LAN access, ports, and security boundaries
Most desktop Clash clients listen on a local port for proxy requests. Common settings include an HTTP port, a SOCKS port, or a mixed port that accepts both HTTP and SOCKS connections. Port numbers vary by client and configuration; 7890 is a common example, not a value to assume. Check the active client settings or configuration and confirm that the core is running before entering a port on another device.
A typical Mihomo configuration for LAN proxy access may look like this:
mixed-port: 7890
allow-lan: true
bind-address: 0.0.0.0
mode: rule
log-level: info
allow-lan: true permits connections from other devices when supported by the running core. The bind address determines which network interfaces accept connections. A loopback-only listener such as 127.0.0.1 is reachable only from the same machine; binding to 0.0.0.0 listens on available IPv4 interfaces. Some clients manage these options through their own settings, so a YAML edit may not be the correct way to make a change persist.
On the client device, the proxy server address is the LAN address of the host computer, not 127.0.0.1. For example, if the host has address 192.168.1.24 and the active mixed port is 7890, a client that supports an HTTP proxy can be configured with server 192.168.1.24 and port 7890. A SOCKS-capable application can use the same port if the listener is a mixed port. If the configuration instead declares separate HTTP and SOCKS ports, use the matching port and protocol.
Allowing LAN access expands the set of devices that can reach the listener. Do not expose the proxy port to the public internet with router port forwarding. On a shared or guest Wi-Fi network, nearby users may be able to connect unless the operating system firewall or network isolation blocks them. Keep the listener limited to the home LAN where possible, and use supported proxy authentication if devices on that LAN are not all trusted. Authentication syntax and availability depend on the core and client version; verify it in the documentation for the version actually installed.
The operating system firewall is a separate gate from the core configuration. On Windows, allow the relevant application or TCP port on a private network profile only; avoid enabling a broad public-network rule. On macOS, check the firewall prompt and confirm that the active network is trusted. On Linux, inspect the host firewall rules as well as the listening socket. A configuration can say “allow LAN” while the firewall still blocks incoming connections.
Set up and test a computer-hosted LAN proxy
The following workflow uses one computer as a proxy host and one other device as a test client. It is deliberately staged: verify local operation first, then expose the listener, then add a single client. This makes it easier to identify whether a failure comes from the core, the firewall, or the client’s proxy settings.
- Confirm that the host works locally. Start the Clash client, select a usable proxy group, and check that the client reports the core as running. Confirm the active HTTP, SOCKS, or mixed port in the client. If the host itself cannot reach a test destination through Clash, fix that before configuring LAN access.
- Find the host’s current LAN address. Check the network details for the Wi-Fi or Ethernet interface actually connected to the home router. An address such as
192.168.1.24or10.0.0.24is typical on private networks, but the exact range depends on the router. Avoid using a VPN interface address, a virtual adapter address, or the loopback address. - Enable LAN listening in the client. Use the client’s “Allow LAN” setting if available, or apply the equivalent supported configuration. Check that the listener binds to the LAN interface, not only to
127.0.0.1. Restart or reload the core if the client requires it, then recheck the displayed port. - Allow only the required inbound traffic. Create or approve a firewall rule for the proxy application or selected TCP port on the private network profile. Do not disable the firewall to test, and do not create a router port-forwarding rule. If the computer has several network interfaces, verify that the rule applies to the home LAN interface.
- Configure one test device. Connect it to the same home LAN, then set its supported HTTP proxy to the host’s LAN address and the active HTTP or mixed port. If it offers a SOCKS setting, choose SOCKS only when the port accepts SOCKS. For a quick command-line test from another computer, use the actual host address and port:
curl --proxy http://192.168.1.24:7890 https://example.com/
Replace the example address and port with the values shown on the host. This command explicitly sends the request through an HTTP proxy; it does not test a SOCKS-only listener. A successful response confirms that this command reached the proxy, but it does not prove that every application on the device uses the same path.
- Check the host’s connection log. Repeat the test with a new destination and look for the connection in the Clash client. Confirm the matched rule and selected proxy group. If the request does not appear, it may not have reached the host at all. If it appears but fails, investigate DNS, rules, the selected node, or the upstream connection.
- Make the host address stable. A DHCP address can change after a router or computer restart. Create a DHCP reservation in the router for the host’s network adapter, or update client settings when the address changes. A reservation is generally easier to maintain than manually assigning an address that could conflict with the router’s DHCP pool.
Use the host’s current address for the first test rather than relying on a device name. Local DNS and name discovery vary between routers and operating systems. After direct-IP access works, a stable local hostname can be convenient if the home network resolves it consistently.
Configure phones, computers, and devices with different proxy support
Desktop operating systems often provide a system proxy switch, but individual applications may ignore it. Browsers and many development tools can use system settings; some command-line programs require environment variables or a command-line option. Others connect directly. When a device can reach the host but an application still bypasses Clash, inspect that application’s proxy behavior instead of repeatedly changing the core port.
Phones and tablets differ by operating system and connection type. A Wi-Fi network’s manual proxy setting commonly accepts an HTTP proxy address and port; it generally does not configure every app to use a SOCKS proxy. Mobile applications may also ignore the Wi-Fi proxy setting, and a manual proxy configured for one Wi-Fi network may not apply to cellular data or another network. For full-device routing on a phone, use a compatible local client or a supported VPN/TUN-based mode rather than assuming that a LAN HTTP proxy captures all traffic.
Televisions, streaming boxes, printers, and game consoles may have limited or no proxy controls. A device’s DNS server setting is not a replacement for a proxy: changing DNS can affect name resolution, but it does not send the device’s traffic through a proxy node. For such devices, use a router or gateway method that explicitly supports their traffic pattern, and decide whether the device should use a proxy policy or connect directly.
Rules still determine what happens after a connection enters the core. In rule mode, a connection is evaluated against the configured rules and then passed to a proxy group, direct route, or other supported policy. LAN sharing does not automatically make every device use the same node or the same behavior. If the household wants different policies for a TV and a laptop, use separate client settings where possible or carefully designed routing policies on the gateway.
- Direct proxy settings: easiest to understand and test; only applications that use the configured proxy are covered.
- Per-device client: offers independent policy selection and may support TUN, but requires installation and permissions on each device.
- Gateway routing: can cover devices without proxy controls, but depends on correct firewall, DNS, and routing integration on the router or gateway.
Do not treat a router’s “use DNS” or “set upstream proxy” option as proof of transparent proxying. Router firmware varies: some can run Mihomo directly, some can only forward traffic to an upstream HTTP proxy, and others require additional routing components. Confirm which traffic is captured, whether IPv4 and IPv6 are both handled, and how local-network destinations are excluded before applying a household-wide policy.
Plan router deployment, failure recovery, and ongoing maintenance
Running a proxy core on a router can be a good fit when the router has compatible firmware, enough memory and storage, and a documented installation method. A dedicated mini PC or always-on gateway is another option when the primary router cannot run the required software. In either case, check the exact architecture and operating-system support for the client and Mihomo build; a package for one processor architecture or firmware release may not run on another.
Before changing router routing, record the current LAN address, DHCP range, DNS settings, and a way to restore the router’s normal configuration. Keep an administrative connection that does not depend on the proxy path. If possible, test the core on a separate device or a small group of clients before applying policy to the whole LAN. Avoid routing the router’s own management traffic through a rule set that could make its control panel unreachable.
Plan exclusions as deliberately as proxy rules. Local network addresses, the router’s management address, printers, file servers, and other private services usually need to remain reachable directly. If DNS is redirected or handled by the gateway, confirm that local hostnames still resolve and that the core’s DNS settings do not create a loop in which DNS requests are sent back into the same resolver path.
For a household setup, a practical rollout is to begin with one test device, then add a second device from a different category, such as a phone after a laptop. Watch the connection log while testing common uses: a normal website, a domain that should use a proxy group, a local network service, and an application that may ignore system proxy settings. Compare the result against the intended policy rather than judging only by whether a page loads.
Keep a small record of the host or gateway address, active proxy port, core version, firewall scope, and the date of the last configuration change. If a subscription update changes node names or groups, check that rules and policy groups still reference valid names. Back up local overrides before updates, and avoid editing generated subscription files when the client provides a supported override mechanism.
For most homes, the least complicated reliable setup is the one that covers the devices that actually need it without exposing unnecessary services. Start with per-device clients when available, use a LAN proxy for a small number of compatible clients, and move to a router or dedicated gateway only when broader coverage justifies the added maintenance. Keep proxy listeners inside the trusted LAN, verify each device in the connection log, and preserve a direct path to manage the host or router if the proxy stops working.