Skip to main content
EN

Home / Blog / Advanced

Sharing your computer's Clash Verge with phones, TVs and consoles

Sharing your computer's Clash Verge with phones, TVs and consoles

One subscription, but a house full of phones, tablets, a TV and a console — installing a client on each is tedious, and some of them cannot run one at all.

The easier path: turn the Clash Verge on your computer into a proxy server for the LAN and point everything else at it.

How LAN sharing is arrangedPhone tablet Clash Verge on the PCLAN access enabledDecided by rulesdirect or via a nodeInternetOnly the computer needs configuring; everything else just needs an address and port
One machine holds the config, the rest just point at it

Step 1: enable LAN access

Find Allow LAN in Clash Verge settings and turn it on.

What that switch does is change the listening address of the proxy port from 127.0.0.1 to 0.0.0.0 — from "only this machine" to "anything on this network".

Step 2: find the computer's LAN address

Windows

ipconfig

Look for the IPv4 Address under "Wireless LAN adapter Wi-Fi" or "Ethernet adapter", usually starting with 192.168. or 10..

macOS / Linux

ifconfig | grep "inet " | grep -v 127.0.0.1

On macOS you can also just read it under System Settings → Network.

Step 3: note the port

Clash Verge Settings → Port settings → look at the Mixed Port, 7897 by default (defaults differ between builds, so read the value on screen).

A mixed port means that one port speaks both HTTP and SOCKS5, so either works.

Step 4: allow it through the firewall

The step people skip. The Windows firewall blocks connections from other machines by default.

The easy way: Control Panel → Windows Defender Firewall → Allow an app through firewall → find Clash Verge → tick the Private column.

The precise way (open just the port):

# run PowerShell as administrator
New-NetFirewallRule -DisplayName "Clash Verge LAN" -Direction Inbound -LocalPort 7897 -Protocol TCP -Action Allow -Profile Private

Step 5: point each device at it

Android phone or tablet

Settings → Wi-Fi → long-press the connected network → Modify network → Advanced options → Proxy: Manual:

  • Hostname: 192.168.1.10 (your computer's address)
  • Port: 7897

iPhone or iPad

Settings → Wi-Fi → tap the ⓘ next to the current network → Configure Proxy → Manual:

  • Server: 192.168.1.10
  • Port: 7897

iOS honours Wi-Fi proxies rather better than Android — Safari and most apps follow it.

Another Windows machine

Settings → Network & Internet → Proxy → Manual proxy setup → turn on "Use a proxy server", enter the address and port.

Another Mac

System Settings → Network → current connection → Details → Proxies → tick "Web proxy" and "Secure web proxy", filling in the address and port for each.

Smart TVs and set-top boxes

Two situations:

TV-class devicesAndroid TV set-top boxesWi-Fi advanced settings configure as for an Android phonesome skins bury it deeplyNo proxy support at allcommon on manufacturer sonly a router-level solution will worksee the next section
Android-based boxes almost always have the setting somewhere

Consoles (PlayStation, Switch, Xbox)

PS5: Settings → Network → Set Up Internet Connection → select your network → Advanced Settings → Proxy Server: Use, then fill in the details.

Switch: Settings → Internet → Internet Settings → select the network → Change Settings → Proxy Settings → Enabled.

Xbox: Settings → Network → Advanced settings has no direct proxy option, so a router-level approach is required.

Devices that cannot set a proxy

Some hardware — certain smart TVs, IoT devices, Xbox — has no proxy setting at all. Two options:

Route A: change the device's DNS and gateway (fiddly)

Point the device's default gateway at the machine running Mihomo and pair that with TUN/TProxy for transparent proxying. That machine needs forwarding configured, and the setup bar is fairly high.

Deploy the Mihomo core on a router or OpenWrt box as a gateway-level proxy. Every device on the network is then covered with no configuration at all.

See getting started with the Mihomo core for the deployment steps.

The two sharing approachesComputer as proxysimple, ten minudies when the computer sleepseach device needs configuringgood for occasional use and few devicesRouter deploymentconfigure once, runs 247zero device configurationneeds a router or an always-on NAS

When a device cannot connect

Work through this:

Diagnostic checklistAllow LAN is actually enabled on the computerThe IP is right (from a phone browser, http:The port matches the mixed port in Clash VergeThe Windows firewall allows the Private profileBoth devices are on the same subnet (both 192.168.1.x)The router does not have AP isolation The computer is not on a VPN that changed its adapter

AP isolation is the one people miss: many routers — especially on guest networks — isolate clients from each other by default, so devices on the same Wi-Fi cannot talk. Turn it off in the router's wireless settings.

Are 5 GHz and 2.4 GHz the same subnet? On most routers yes, but if you have a guest network or band separation with VLANs, they may not be. Try putting both devices on the same SSID.

Turn it off when you are done

Disable Allow LAN when you are not using it. While it is on, anything that can reach your LAN can use the proxy — including a neighbour who got onto your Wi-Fi.

In short

Four things make LAN sharing work: enable allow-lan, fix the computer's IP, open the firewall, and enter the right port on each device.

If you have many devices and want it to be reliable, a router deployment is the better long-term answer.

Related: port settings explained and deploying the Mihomo core.