This guide walks through using v2rayN on a Windows PC with an Android phone, tablet, or TV on the same home network. Learn how to find the listening address and port, configure Windows Firewall, and set up proxies on other devices. Get v2rayN working on the PC first, allow access only from the required subnet, then verify the route with an explicit proxy request and the logs. No public port forwarding on your router is needed.
1. How LAN proxy sharing works
“Allow connections from the local network” in v2rayN lets other devices connect to the proxy inbound on your PC. Requests from your phone go to the PC, where the running core applies its routing rules to choose a direct or proxied connection. A subscription provides node configuration; enabling sharing does not create nodes or install a client on other devices.
This setup works only for apps that honor the device’s proxy settings. Android’s manual Wi-Fi proxy is typically an HTTP proxy, and not every app is guaranteed to use it. Games, some TV apps, and apps that create their own connections may bypass the setting. Enabling TUN on the PC also does not automatically route all traffic from other devices on the subnet.
- Good for: Temporarily sharing the PC’s connection with a phone browser or a proxy-compatible TV app while the PC stays on.
- Requirements: Devices can reach each other, the PC’s node works, and the proxy listener and firewall rules are configured correctly.
- Limitations: This is not a router gateway setup, and it does not route every connection from your phone through the PC.
2. Find the PC’s LAN IP and actual listening port
Select a working node on the PC and confirm that v2rayN can reach a website. Then open “Settings” → “Parameter settings” and find the local listening ports and “Allow connections from the local network.” Labels and sections can vary between versions, so use the fields shown in your installed version rather than guessing from an older guide.
- Note the port for the HTTP, SOCKS, or mixed inbound. If the settings show only a mixed port, confirm that it accepts both HTTP and SOCKS requests.
- Enable “Allow connections from the local network” and save. If prompted to restart the core, do so, then check the logs for bind failures or port conflicts.
- In Windows Terminal, run
ipconfig. Find the Ethernet or Wi-Fi adapter currently connected to the network and note its IPv4 address. - Ignore disconnected adapters, virtual machine adapters, and TUN adapters. This guide uses
192.168.1.20as the PC’s example address and10808as an example mixed port confirmed to accept HTTP and SOCKS.
PC settings to note
- LAN IPv4 address
192.168.1.20- Mixed inbound port
10808/TCP- LAN connections
- Enabled
- Network range
192.168.1.0/24
These examples are used throughout the guide. Replace them with your actual address, subnet mask, and port.
Settings for other devices
- Server
192.168.1.20- Port
10808- Protocol
- HTTP, or SOCKS5 if supported by the app
- Authentication
- Use the settings configured for the PC’s inbound
Enter only the address in the server field—not a subscription URL, node domain, or protocol prefix.
127.0.0.1 is the loopback address of each individual device. Entering it on your phone connects to the phone itself, not the PC. 0.0.0.0 means listening on all IPv4 interfaces; it is not the destination address to enter on your phone. Addresses assigned by home routers can change. For a stable address, reserve an IP lease for the PC in your router’s DHCP settings.
3. Check the listener, then allow the subnet through Windows Firewall
Run the following command in Windows PowerShell to check the example port. If your port is different, replace 10808 first. Enabling the setting alone is not enough—the core must actually listen on an address reachable from the LAN.
Get-NetTCPConnection -State Listen -LocalPort 10808 |
Select-Object LocalAddress, LocalPort, OwningProcess127.0.0.1: Accessible only from the PC. Check the LAN setting and confirm the core restarted successfully.0.0.0.0or the PC’s LAN IPv4 address: The listener can accept connections on the corresponding IPv4 interfaces; check Windows Firewall as well.- Only
::: This is an IPv6 wildcard listener. Whether it also accepts IPv4 depends on the socket configuration, so test using the IPv4 address too. - No output: Check that the core is running, confirm the actual port, and see whether another program is using it.
On a trusted home network, open “Settings” → “Network & Internet” → the connected network’s properties and set the network profile to “Private.” Do not change a public network to private just to share a proxy. Next, go to “Windows Security” → “Firewall & network protection” → “Advanced settings” → “Inbound Rules.” Create a TCP port rule, limit it to the Private profile, and specify the permitted remote subnet under Scope.
The following equivalent PowerShell example requires administrator privileges and applies only if the PC and other devices are on 192.168.1.0/24. /24 corresponds to the subnet mask 255.255.255.0. Change the range if your network differs; do not use this example unchanged.
New-NetFirewallRule `
-DisplayName "v2rayN LAN TCP 10808" `
-Direction Inbound `
-Action Allow `
-Protocol TCP `
-LocalPort 10808 `
-RemoteAddress 192.168.1.0/24 `
-Profile Private4. Configure the proxy on an Android phone, tablet, or TV
Connect the devices to a network where they can reach the PC. The PC can use Ethernet while the phone uses Wi-Fi; what matters is that the router does not isolate them. Being on the same Wi-Fi network name does not guarantee connectivity—guest networks and AP isolation can block device-to-device traffic.
- Android phone or tablet: Go to “Settings” → “WLAN” or “Wi-Fi” → your current network’s details → “Modify network” → “Advanced options,” then set Proxy to “Manual.” Menu names vary by device and Android version.
- Set up an HTTP proxy: Enter
192.168.1.20as the proxy hostname and10808as the port, provided you have confirmed that the port accepts HTTP requests. For the first test, do not add proxy bypass rules. Save the settings and reopen your browser. - TV system: Look for proxy settings in the advanced options for the current network. If the TV has no system-wide proxy option, configure it within a specific app that supports proxies. Do not assume changing settings on the PC will configure the TV.
- If the app supports SOCKS5: Select SOCKS5, enter the same PC address, and use the actual SOCKS or mixed port. If the app offers remote DNS, enable it if needed and test again.
Android’s manual HTTP proxy settings usually have no username or password fields. If the PC’s inbound requires authentication and the device cannot provide credentials, entering only the address and port will not work. Use an app that supports the required authentication instead. Do not bypass this limitation by disabling authentication on an untrusted network.
Troubleshoot: Test the browser first, then the target app
If the browser works but a TV app still fails, first check whether the app honors the system HTTP proxy. Avoid changing nodes, subscriptions, or firewall rules right away; that can turn an app compatibility issue into several configuration problems.
5. Verify the shared route with an explicit proxy request
Internet access from the PC only confirms that its own connection works. Test sharing from another device. If another Windows PC is on the LAN, first test the port, then use curl.exe with an explicit proxy to request a sample webpage. Keep the sharing PC and v2rayN running during the test.
Test-NetConnection 192.168.1.20 -Port 10808
curl.exe --proxy http://192.168.1.20:10808 --connect-timeout 5 --max-time 20 -I https://example.com/
curl.exe --proxy socks5h://192.168.1.20:10808 --connect-timeout 5 --max-time 20 -I https://example.com/These two curl commands test the HTTP and SOCKS5 paths, respectively. Use each only if the inbound supports that protocol. socks5h resolves the destination hostname through the proxy; with ordinary socks5, the test device usually resolves it first. The 5-second connection timeout and 20-second total timeout are test limits, not measured latency or speed.
| Test result | What it tells you | Next step |
|---|---|---|
TcpTestSucceeded: False | Device could not establish a TCP connection | Check the IP address, listener, firewall, and device isolation |
| Port test succeeds, but HTTP proxy request fails | Only confirms that TCP is reachable | Check the port protocol, authentication, and core logs |
Returns 407 | The proxy requires authentication | Check that the device supports authentication and sends the correct credentials |
| Returns response headers from the target website | The request reached the proxy and was completed | Test again with the actual app and target website |
| Command works, but an app fails | The shared proxy endpoint is basically working | Check the app’s proxy support and DNS behavior |
Check the v2rayN core logs as well. Look for the destination hostname, inbound connection, and outbound selection at the time of the test; the details available depend on your logging settings. Passing through the PC’s proxy does not guarantee that a request uses a remote node—the routing rules may still send it direct. To verify the egress, compare the logs with results from a trusted IP lookup service; do not rely only on whether a webpage loads.
6. Common LAN sharing questions
My phone and PC are on the same router. Why does the connection still time out?
First, make sure the address entered on the phone belongs to the physical network adapter the PC is actually using. Then check for a guest network, wireless client isolation, or rules that block traffic between subnets. Finally, confirm that the current Windows network profile matches the firewall rule. If the rule applies only to Private networks, it will not allow traffic under the Public profile.
Websites load on my phone, but games or video apps do not use the proxy. Why?
A Wi-Fi HTTP proxy does not guarantee that every app will use it, and it does not provide support for arbitrary UDP traffic. Check whether the app has its own proxy settings. If an Android device needs to run a client independently, see the v2rayNG or v2flyNG setup guides as needed. That is a separate way to connect the device, not a reason to broaden the PC’s firewall rules.
Can sharing continue if I turn off the PC’s system proxy?
Usually, yes. The system proxy setting controls how apps on the PC that honor it connect; LAN sharing depends on the running core and its inbound listener. Other devices can keep using the proxy as long as the core is running and the listener and firewall rules remain active. Exiting v2rayN or stopping the core will interrupt sharing.
It worked yesterday, but my phone suddenly has no connection today. What should I do?
First, check whether the PC is asleep and whether v2rayN is running. Then run ipconfig again to see if the address changed. If you are not sharing the proxy for now, set Proxy to “None” in the phone’s current Wi-Fi settings. Otherwise, the phone will keep trying to connect to a PC that is offline or has a new address.
7. Restore device settings when you stop sharing
When you finish sharing, first turn off the proxy on your phone, tablet, and TV. Then disable LAN connections in v2rayN and restart the core if prompted. Finally, delete the firewall rule you created for sharing so it does not leave an unnecessary access point behind.
Remove-NetFirewallRule -DisplayName "v2rayN LAN TCP 10808"- Confirm that the other devices can connect directly again and that their browsers no longer try to use the old proxy address.
- Check the listening address again and confirm the LAN endpoint is disabled or accessible only from the PC.
- For long-term sharing, note the actual IP, port, allowed subnet, and authentication method. Retest after changing router or core settings.