This guide is for users with a working node who want phones or TVs on the same home network to use their PC’s proxy. The setup involves four steps: let v2rayN listen on a LAN address, find the PC’s IPv4 address and inbound port, allow access through the firewall only on trusted networks, and configure the proxy on the other device. Examples use a Windows PC and an Android device. Replace all sample addresses and ports with your actual settings.
1. How LAN Proxy Sharing Works
v2rayN manages nodes, subscriptions, and routing on your desktop; the selected core handles the actual connections. When sharing a proxy, your phone does not read the subscriptions on your PC or need copied VMess or VLESS node details. Instead, it sends requests to an HTTP or SOCKS inbound opened by the PC. The PC then routes each request to a direct or proxy outbound according to v2rayN’s routing rules.
“Allow connections from the LAN” changes the inbound listening scope. When v2rayN listens only on 127.0.0.1, only the PC itself can connect. Listening on a LAN interface or on 0.0.0.0 for all IPv4 interfaces lets other devices connect, provided the network allows it. The latter is not the server address to enter on your phone, and it does not mean the firewall is open.
- PC system proxy: Applies to apps on the PC that follow the system proxy settings. It does not configure phones or TVs.
- LAN proxy inbound: Other devices must be configured to use the PC’s address and port, and the app must support that proxy.
- TUN on the PC: This does not make the PC a transparent gateway for your home network. Enabling TUN on the PC alone does not ensure that TV traffic passes through it.
2. Allow LAN Connections and Check the Port
First select a working node on the PC and confirm that you can browse normally. Then set up sharing. This helps distinguish an unavailable node from an unreachable LAN inbound. The steps below use common v2rayN menu names. Menu locations may vary across versions and between the desktop and WPF interfaces; check the current settings and core logs to confirm what each port is for.
- Open v2rayN and go to “Settings” → “Parameter Settings”. Find the basic settings or the “Core: Basic Settings” section.
- Find and enable “Allow connections from the LAN”. If the interface also offers a LAN listening address, select the actual local network interface or, on a trusted network, the option to listen on all interfaces.
- Note the local listening port and its type. A common setup uses
10808for SOCKS and10809for HTTP. Some versions or core configurations use a single mixed port for both HTTP and SOCKS. - Save the settings and wait for the core to restart. If it does not reload automatically, use the client’s service restart option, or exit v2rayN normally and reopen it.
- Check the logs for errors such as a failed listener or an address already in use. Do not assume sharing is working just because the setting is enabled.
In Windows Command Prompt, use the command below to check the sample ports. If you changed the ports, update the numbers in the command too.
netstat -ano | findstr ":10808"
netstat -ano | findstr ":10809"| Example listener | What it means | Next step |
|---|---|---|
127.0.0.1:10809 | Accepts IPv4 connections from this PC only | Check that the LAN setting took effect and reload the core |
0.0.0.0:10809 | Listens on all IPv4 interfaces | Check the firewall and connectivity from other devices to the PC |
192.168.1.20:10809 | Listens only on a specific LAN interface | Make sure the phone can reach the network on that interface |
No matching LISTENING entry | Port mismatch or service failed to start | Check the settings, logs, and port usage |
Compare the PID in the command output with the process details in Task Manager to avoid mistaking another program’s listener for the v2rayN core. If you see only an IPv6 listener, test IPv4 connectivity separately; one output line does not tell you whether dual-stack connections work.
3. Find Your PC’s Local IP and Configure a Phone or TV
Run ipconfig in Windows Command Prompt. Find the “Wireless LAN adapter” or “Ethernet adapter” currently connected to your router and note its IPv4 address. Do not use a virtual adapter, loopback address, or disconnected adapter. For example, assume the PC is 192.168.1.20, the phone is 192.168.1.35, and both are on a network with the subnet mask 255.255.255.0. These addresses are examples only.
Manual proxy settings for Android Wi-Fi
- Proxy type
- HTTP
- Server hostname
192.168.1.20- Server port
10809, or your actual HTTP inbound port- Applies to
- Currently saved Wi-Fi network
Enter only the IP address as the hostname; do not add a protocol prefix. Enter the port separately.
Apps that support SOCKS
- Proxy type
- SOCKS5
- Server address
192.168.1.20- Server port
10808, or your actual SOCKS inbound port- DNS lookup
- Prefer resolving through the proxy, if supported by the app
An app-specific proxy affects only that app, not the entire device.
Where to find manual proxy settings on Android
- Go to “Settings” → “WLAN” or “Wi-Fi”, then open the current network’s details or edit screen.
- Expand “Advanced options” → “Proxy” → “Manual”. On some devices, the proxy setting is at the bottom of the network details page.
- Enter the PC’s IPv4 address and HTTP port, then save and reopen the browser to test. For a mixed inbound, enter its actual port.
- This Wi-Fi proxy setting usually does not apply when you switch to mobile data. It may still be saved when you reconnect to the same Wi-Fi network.
Check whether your TV offers proxy settings
Some Android TVs let you open the current Wi-Fi network under “Network & Internet” and enter a manual proxy in its advanced settings. Others do not offer this option, or only some apps support proxy settings. If the option is available, enter the HTTP host and port. If it is not, do not enter the PC’s address as the DNS server or default gateway; those are different network settings.
- The PC can use Ethernet while the TV uses Wi-Fi, as long as the router allows devices on both networks to communicate.
- Devices using the same Wi-Fi name may still be unable to communicate. Guest networks and AP isolation can block connections.
- HTTPS websites typically use the CONNECT method over an HTTP proxy to create a tunnel. You do not need to switch to the SOCKS port for HTTPS.
- A manual Wi-Fi proxy does not guarantee that every app or UDP connection will pass through the PC. It depends on whether the app follows the proxy settings.
4. Limit Access in Windows Firewall
If the listener is set up correctly but other devices still cannot connect, check Windows Firewall. You can set a home network to “Private” once you have confirmed it is safe, but do not switch a public network to Private just to share a proxy. Disabling the firewall entirely is also not recommended, as it removes protection from unrelated services too.
- Open “Windows Security” → “Firewall & network protection” → “Advanced settings”.
- Select “Inbound Rules” → “New Rule” → “Port”, choose TCP, and enter the actual inbound port, such as
10809. - Choose to allow the connection, select only the “Private” profile used by your trusted network, and give the rule a descriptive name.
- In the rule properties, go to “Scope” → “Remote IP address” and restrict access to the local subnet, or more narrowly to the actual IP addresses of your phone and TV.
- If your device uses SOCKS or another mixed port, add a separate rule for that actual TCP port. Do not open a large range of ports.
If you are comfortable with PowerShell, you can also run the example below in an administrator window. It allows TCP 10809 only on the Private profile and only from the local subnet. It does not replace the listener settings above. This rule will not help if the port or network profile is different.
New-NetFirewallRule -DisplayName "v2rayN LAN HTTP 10809" `
-Direction Inbound -Action Allow -Protocol TCP `
-LocalPort 10809 -Profile Private -RemoteAddress LocalSubnet5. Test in Layers: An Open Port Does Not Mean the Proxy Works
Start with the layer closest to the PC. First confirm that the PC can use the selected node, then test the LAN TCP connection, and finally verify the proxy protocol and web access. A successful ping to the PC does not prove that the proxy works: ICMP and TCP ports are different things to test, and the PC may block one but not the other.
| Check | What to do | What the result means |
|---|---|---|
| PC and node | Visit a website on the PC using its configured proxy | If it fails, troubleshoot the node, routing, or PC network first |
| LAN port | Run a TCP port test from another Windows device | Success only confirms that a connection to the port can be established |
| Proxy protocol | Send a request explicitly using HTTP or SOCKS5 | If it fails, check the protocol, port, and proxy authentication settings |
| Device app | Save the Wi-Fi proxy settings and reopen the browser | If the browser works but another app does not, check whether the app supports proxies |
If there is another Windows PC on the LAN, run the tests below in PowerShell on that device. The first checks the port; the next two send requests to this site’s homepage through the HTTP and SOCKS5 inbounds. Run only the command that matches your configuration.
Test-NetConnection -ComputerName 192.168.1.20 -Port 10809
curl.exe --proxy http://192.168.1.20:10809 --connect-timeout 5 --max-time 15 -I https://v2rayclub.com/
curl.exe --socks5-hostname 192.168.1.20:10808 --connect-timeout 5 --max-time 15 -I https://v2rayclub.com/TcpTestSucceeded : True means the TCP connection succeeded. An HTTP response also confirms that the request passed through the specified inbound. Neither result proves that routing selected a remote node; the domain may be routed directly by your rules. Check the connection details or core logs on the PC to verify the source device, destination domain, and selected outbound.
Diagnosis: If the port test fails, check the LAN before switching nodes
If the TCP test fails, first check the listening address, firewall, device subnet, and router isolation. Check the node and routing only if the inbound request reaches the PC but fails at the outbound stage. This order helps avoid mistaking network isolation for a subscription problem.
The --socks5-hostname option above lets the proxy resolve the destination domain, while some apps resolve it locally. If the same domain behaves differently across apps, check the DNS resolution method and v2rayN’s DNS and routing rules. Do not set the system DNS server to the PC’s proxy port. For details, see DNS configuration.
6. Common Questions About Sharing a Proxy with Phones and TVs
The PC works, but my phone keeps saying it can’t connect. What should I check first?
First, make sure the phone is using the PC’s current IPv4 address, not 127.0.0.1. Then check that the HTTP port is listening, the LAN setting was applied successfully, and the firewall rule matches the current Private network. If the phone is on guest Wi-Fi, switch it to a home network that allows devices to communicate.
The proxy works in my phone’s browser, but the TV’s video app still won’t connect. Why?
First, test on the TV with a browser that follows the proxy settings. If the browser works, the video app may ignore the system HTTP proxy or use traffic that the current setup does not capture. Check whether the app has its own proxy settings. Repeatedly changing the PC’s system proxy or enabling TUN on the PC will not help if the app does not use a proxy.
It stopped working after I restarted my PC. Do I need to import the subscription again?
Run ipconfig and check whether the IPv4 address changed. Then make sure v2rayN is running and the port is listening. On a home router, you can reserve an address through DHCP for the PC’s network adapter so your phone and TV do not need new proxy host settings whenever the lease changes. An IP address change is unrelated to subscription contents.
My phone loses its connection when the PC goes to sleep. How do I restore it?
Wake the PC and make sure the core is running again, or set the proxy to “None” in the phone’s current Wi-Fi settings. Exiting v2rayN, switching the PC’s network, or shutting down the PC will make the shared proxy unavailable. If you use sharing often, adjust the sleep settings for when the PC is plugged in as needed; there is no need to permanently disable all power-saving features for occasional use.
Do I need to install a client on my phone and copy the subscription?
No additional client is needed if you only use a Wi-Fi HTTP proxy. To connect independently when your phone is away from the PC, choose v2rayNG or v2flyNG from the downloads page and use a compatible configuration from your service provider. This is a standalone client connection and no longer depends on the PC’s LAN inbound.
7. Checklist for Stopping Sharing and Keeping It Secure
Enable the shared proxy only when needed. Recheck who can access it when you add devices at home, move the PC to another network, or let someone connect to your Wi-Fi temporarily. The PC’s proxy routing also affects those devices: requests matched to a direct route remain direct. Setting a proxy does not guarantee that every request uses the same remote exit.
- Stop sharing: First set the Wi-Fi proxy to “None” on your phone and TV, then disable “Allow connections from the LAN” in v2rayN, save, and reload the core.
- Remove the rule: Disable or delete the firewall rule created for sharing, leaving other system rules unchanged.
- For regular use: Reserve a stable PC IP through DHCP on your router, note the actual inbound type and port, and limit which devices can connect.
- When changing networks: Disable sharing before connecting to a public or untrusted network. Do not rely on a single firewall rule as your only protection.
- Keep troubleshooting notes: Record whether the failure occurs at the port connection, proxy protocol, or outbound stage. Before sharing logs, remove subscription links, server details, and other sensitive information.
To adjust subscriptions and outbound rules, see subscription management. If you have not yet connected from the PC, follow the usage guide to install the client and import a node first, then return to the LAN sharing steps.