v2rayN Allow LAN Connections: Share Your PC Proxy with Phones and TV Boxes

1. LAN proxy vs. routing all device traffic

When your phone and PC are connected to the same trusted home network, the phone can send proxy-aware requests through v2rayN on the PC. The PC then routes them directly or through a proxy according to its current rules. Sharing an endpoint does not mean every request goes through a remote server; the route depends on the domain, IP address, and routing rules.

“System proxy” and “Allow connections from the LAN” are two separate v2rayN settings. The first lets apps on the PC use its local proxy settings; the second changes which interfaces the proxy listens on. Enabling the system proxy on the PC alone may not let your phone connect. Enabling LAN listening alone will not configure the proxy address on your phone.

• Works with: Browsers, apps that follow the system HTTP proxy, and apps that let you enter a proxy server manually.
• Not guaranteed to work with: Apps that ignore the system proxy, game traffic over UDP, some media players, and standalone DNS requests.
• Requirements: The PC must stay powered on with the v2rayN core running, and the devices must not be isolated from each other by a guest network.

2. Enable LAN listening in v2rayN and check the port

First, select an available server on your PC and confirm that your browser can reach the target site through the proxy. Then open “Settings” → “Parameter settings” in v2rayN and look for “Allow connections from the LAN” under Basic settings or the inbound-related section. Turn it on and save. The tabs and labels vary slightly between desktop versions, so follow the interface in your installed version. If the setting does not take effect right away, restart the core and check the listening status again.

1. Note the local listening port shown in the interface and its protocol.
2. Turn on “Allow connections from the LAN” and save. If prompted to restart the core, do so.
3. Check the logs for port conflicts or startup failures. If the core is not running, resolve the error before changing settings on your phone.
4. Run the command below to check the listening address and confirm that the port is not bound only to the loopback address.

netstat -ano | findstr LISTENING | findstr ":10808"

The examples below use 10808 as a mixed port that supports HTTP. Some configurations use separate SOCKS and HTTP ports—for example, SOCKS on 10808 and HTTP on 10809. Android Wi-Fi’s “Manual proxy” option usually requires an HTTP endpoint; the port number alone does not tell you which protocol it uses. If your HTTP port is 10809, update the port in both the device settings and the firewall rule below.

The output in the table is for reference; your PC does not need to show the exact same result. If you only see [::]:10808, also verify that the listener accepts IPv4 connections. This line alone does not prove that your phone can reach it.

3. Find your PC’s local IP address and choose the right adapter

In Windows Terminal, run ipconfig and find the IPv4 address and default gateway for the active “Wireless LAN adapter WLAN” or “Ethernet adapter.” Do not use a virtual adapter, a disconnected adapter, or 127.0.0.1. A loopback address entered on your phone points to the phone itself, not your PC.

ipconfig

A wired PC and a wireless phone on the same router can usually communicate, and they do not need to use the same band (2.4 GHz or 5 GHz). What matters is whether the router places them on networks that can communicate with each other. Guest Wi-Fi, AP isolation, and separate VLANs can block the connection. If your PC’s address changes after every restart, reserve its DHCP address in the router to avoid repeatedly updating the phone.

4. Allow the connection through Windows Firewall on private networks only

If the port is listening but your phone keeps timing out, first check the Windows network profile. On a trusted home network, go to “Settings” → “Network & Internet” → your current Wi-Fi or Ethernet connection and set the network profile to “Private.” Do not switch a public network to Private just to share a proxy, and do not turn off the entire firewall.

1. Open “Windows Security” → “Firewall & network protection” → “Advanced settings.”
2. Select “Inbound Rules” → “New Rule” → “Port,” choose TCP, and enter the actual HTTP or mixed listening port.
3. Choose “Allow the connection,” select “Private” only, and name the rule v2rayN LAN TCP 10808.
4. Open the rule properties, go to “Scope,” restrict remote IP addresses to “Local subnet,” and save.

If you are comfortable with PowerShell, you can create the equivalent rule in an administrator terminal. The example uses port 10808; use just one method to avoid duplicate rules.

New-NetFirewallRule -DisplayName "v2rayN LAN TCP 10808" `
  -Direction Inbound -Action Allow -Protocol TCP `
  -LocalPort 10808 -Profile Private -RemoteAddress LocalSubnet

5. Set up a manual proxy on an Android phone or TV box

On most Android phones, open “Settings” → “Wi-Fi” or “Network & Internet” → your current network → “Modify network” → “Advanced options” to find the proxy settings. Set “Proxy” to “Manual,” enter your PC’s local IP address as the proxy hostname, and use the confirmed HTTP or mixed port. Some manufacturers require tapping the gear or edit button next to the network first.

• Proxy hostname: For example, 192.168.1.20. Do not add http:// or include the port in this field.
• Proxy port: For example, 10808. Use the port configured on your PC.
• Bypass proxy for: Leave this blank for the initial test. Once the proxy works, add local network addresses if needed.
• Test after saving: Close and reopen your browser, then visit an HTTPS page you have already tested on your PC.

On an Android TV box, look under “Settings” → “Network & Internet” → your current Wi-Fi network → “Proxy settings,” then select “Manual.” Whether proxy settings are available for wired connections depends on the system. If there is no proxy field, check whether the specific app supports its own proxy settings. Do not confuse “Static IP” with “Proxy settings”; changing the gateway or DNS at random can disconnect the device.

A manual Wi-Fi proxy applies only to that network and will not carry over when you switch to mobile data. Even if the browser works, a TV streaming app may ignore the system proxy entirely. If you need the Android device to establish its own proxy connection, consider v2rayNG or v2flyNG instead of continuing to change the PC’s listening port.

6. Troubleshoot by checking TCP connectivity, proxy protocol, and routing

Do not assume the proxy is working just because ping succeeds. ICMP and TCP are governed by different firewall rules, and a failed ping does not necessarily mean the proxy port is unreachable. A better sequence is to check the port connection first, then test an HTTP proxy request, and finally confirm that the request followed the expected outbound route.

# Check the port from another Windows PC on the same LAN
Test-NetConnection 192.168.1.20 -Port 10808

# Check whether the HTTP proxy can establish an HTTPS connection
curl.exe --proxy http://192.168.1.20:10808 --connect-timeout 5 --max-time 20 -I https://www.microsoft.com/

Pay close attention to TcpTestSucceeded in the first command. The second command sets a 5-second connection timeout and a 20-second overall time limit, helping distinguish an unreachable port from a slow response after connecting. Redirects or access-denied responses from the site also need to be checked against the logs; do not rely on a single status code. If you do not have a second PC, send a request from your phone’s browser while watching the core logs on the PC. To review access records, first confirm that the relevant logging is enabled in the current settings.

7. Common questions and cleanup

If you created the rule using the PowerShell command above, remove it by running the following command in an administrator terminal. Before sharing long-term, make sure the network is trusted and the address is stable, and note the port in use so you can remove outdated settings if you later change the client’s inbound configuration.

Remove-NetFirewallRule -DisplayName "v2rayN LAN TCP 10808"