v2rayN LAN Proxy Setup: Share Your PC’s Connection with Phones and TVs

At a glance

This guide uses a Windows PC running v2rayN, an Android phone, and a TV on a home network to walk through the PC’s outbound connection, LAN listener, Windows Firewall, and device proxy settings. The key is to distinguish the PC’s address from the proxy port and understand which apps support proxies. Once configured, you can check whether requests reach the PC instead of relying on a device’s “Connected” status.

How sharing works: devices connect to the proxy on your PC

In v2rayN, “Allow connections from the LAN” controls whether other devices can connect to the local proxy. Your phone doesn’t need the remote node’s VMess or VLESS settings; it uses the PC as an HTTP or SOCKS proxy. The client and core on the PC handle the remote protocol, TLS settings, and routing rules.

Device proxy request LAN connection Route rule matching PC proxy outbound Response from destination

This setting doesn’t turn your router into a transparent proxy or enable internet connection sharing. Only apps on your phone or TV that honor the proxy settings will use the PC; apps without proxy support may connect directly. Enabling TUN on the PC also won’t automatically route traffic from other devices on your home network.

Requirements: The node on the PC must be working, the client and core must be running, and the device must be able to reach the PC’s LAN address.
Network setup: Wired and wireless devices on the same home router can usually communicate, but guest networks, Wi-Fi client isolation, or separate VLANs may block connections.
Availability: The proxy stops working when the PC is off, asleep, disconnected from the network, or no longer running the core.
Limitations: An HTTP proxy mainly handles TCP requests from apps that honor proxy settings. This doesn’t mean games, screen casting, or all UDP traffic will be routed through it.

Step 1: Find your PC’s address and enable the LAN listener

First, select a working node on the PC and confirm that you can access the internet in a local browser. Then open a terminal, run ipconfig, and find the IPv4 address under the Wi-Fi or Ethernet adapter you’re using. Don’t use a virtual adapter or loopback address, and don’t mistake the default gateway for your PC’s address.

ipconfig

Example network details:
PC IPv4 address: 192.168.50.10
Subnet mask: 255.255.255.0
Default gateway: 192.168.50.1
Phone IPv4 address: 192.168.50.23
TV IPv4 address: 192.168.50.30

In v2rayN, go to “Settings” → “Parameter settings” and look for “Allow connections from the LAN” or “Allow LAN connections.” Enable the option and save. The setting may be grouped differently across desktop interfaces and versions, so follow the wording in your version. Note the local HTTP, SOCKS, or mixed port. Restart the service if prompted so the new listener takes effect.

Note the PC’s current IPv4 address. The examples below use 192.168.50.10; replace it with your PC’s actual address.
Note the port and its protocol. This guide uses HTTP on 10809 and SOCKS on 10808 as examples; these are not guaranteed defaults across versions.
If the interface offers only one mixed port, first confirm that it supports both HTTP and SOCKS, then use that same port for both proxy types.
Check the logs after saving. If the port is already in use, resolve the conflict; the toggle alone doesn’t confirm that the service started.

Step 2: Check the listening port and allow access through Windows Firewall

Check the listener in Windows PowerShell. The commands below use the two example ports in this guide; replace the numbers if you use different ports. No output usually means nothing is listening. If you see only 127.0.0.1, other devices still can’t connect over IPv4.

Get-NetTCPConnection -State Listen |
  Where-Object { $_.LocalPort -in 10808,10809 } |
  Select-Object LocalAddress,LocalPort,OwningProcess

If the output shows 0.0.0.0 or the PC’s actual IPv4 address, check the firewall next. If you see only ::, test IPv4 connectivity instead of assuming dual-stack listening works. On a trusted home network, go to “Settings” → “Network & Internet” → the active connection’s properties to check its network profile. Don’t switch a public network to private to bypass restrictions.

Press Win + R, enter wf.msc, and open Windows Defender Firewall with Advanced Security.
Go to “Inbound Rules” → “New Rule” → “Port,” select TCP, and enter the proxy port you’re actually using.
Allow the connection, select only the applicable “Private” profile, and give the rule a name so you can remove it later.
Open the new rule’s “Properties” → “Scope” and limit remote IP addresses to your phone and TV, rather than opening access to the entire network.

You can also create an equivalent restricted rule in an elevated PowerShell window. The commands below are only for the example addresses and ports above; replace each value before running them. They won’t enable port forwarding on your router, and there’s no need to turn off Windows Firewall.

New-NetFirewallRule `
  -DisplayName "v2rayN LAN TCP restricted" `
  -Direction Inbound `
  -Action Allow `
  -Protocol TCP `
  -LocalAddress 192.168.50.10 `
  -LocalPort 10808,10809 `
  -RemoteAddress 192.168.50.23,192.168.50.30 `
  -Profile Private

Verify port access before changing device settings

If the LAN TCP connection can’t be established, changing subscriptions, switching nodes, or editing the remote protocol won’t fix the inbound connection. Check the listening address and firewall scope first, then troubleshoot proxy support in the app.

Step 3: Choose the right proxy type on your phone and TV

On Android, the usual path is “Settings” → “Network & Internet” → “Internet” → current Wi-Fi network → edit network → “Advanced options” → “Proxy” → “Manual.” Some manufacturers put this under the Wi-Fi details page. Android’s manual Wi-Fi proxy setting usually expects HTTP; don’t enter a port that accepts SOCKS only.

System Wi-Fi: HTTP proxy

Proxy type: Manual HTTP
Server: 192.168.50.10
Port: 10809, example HTTP port
Use with: Wi-Fi proxy settings on a phone or TV

Enter only the address in the server field—don’t add http://. Enter the port separately and use the value the PC is actually listening on.

In-app settings: SOCKS5 proxy

Proxy type: SOCKS5
Server: 192.168.50.10
Port: 10808, example SOCKS port
Use with: Apps with explicit SOCKS5 support

Use this option only if the app offers SOCKS5 settings. The app must also support resolving remote domain names through the proxy.

If your TV’s Wi-Fi details include proxy settings, use the HTTP values shown above. Wired and wireless connections may save settings separately. If the TV’s system has no proxy option, check whether the app has its own proxy settings. A phone working on the same Wi-Fi doesn’t mean every TV app supports proxies.

HTTPS websites: They usually use the CONNECT method to create a tunnel through an HTTP proxy. You don’t need to change the server field to an HTTPS URL or install a certificate on the device.
Proxy bypasses: If you need direct access to your router’s admin page or a local service, configure an exception using syntax supported by your device. Wildcards and subnet formats vary by system, so don’t copy settings from another platform without checking.
DNS resolution: HTTP proxies and SOCKS5 handle domain names differently. Whether SOCKS5 sends a domain name to the PC for resolution depends on the app’s settings; the protocol name alone doesn’t tell you.

Step 4: Test the connection and routing in stages

Start by testing the LAN port, then the proxy handshake, and finally access to the destination and routing. Internet access on the PC confirms only that its local connection works. A phone showing that it’s connected to Wi-Fi doesn’t prove its requests are reaching the PC’s proxy.

Check	What to do	What it tells you
Network connectivity	Check the PC and device addresses, gateway, and guest network settings	Being on the same subnet doesn’t guarantee devices can communicate
Inbound TCP	Test the port from another Windows device	A successful test confirms only that a TCP connection can be made
Proxy handshake	Send a request explicitly over HTTP or SOCKS5	Rules out apps that aren’t using the system proxy
Routing and outbound	Check the matching outbound in the core’s access logs	Requests can still go direct after reaching the proxy

If you have another Windows device, run the commands below there. Don’t test only from the PC running the proxy: a successful local connection doesn’t replace a test from another device. The example websites are test targets only; their responses don’t guarantee speed or availability.

Test-NetConnection 192.168.50.10 -Port 10809

curl.exe --head --connect-timeout 10 --max-time 20 `
  --proxy http://192.168.50.10:10809 https://v2ray88.com/

curl.exe --head --connect-timeout 10 --max-time 20 `
  --proxy socks5h://192.168.50.10:10808 https://v2ray88.com/

TcpTestSucceeded: True means the TCP port is reachable; it doesn’t confirm that the remote node is working. The socks5h option requires the proxy to resolve the destination domain. The HTTP command accesses an HTTPS destination through the proxy. If you get an HTTP status code from the destination, that usually means an application-level response was received. Even if the status isn’t successful, check the response source and logs before changing the listener settings.

Common issues: port timeouts, working browsers, and TVs connecting directly

Your PC works, but the phone times out after you set the proxy?

Check that the phone is using the PC’s address, not the gateway, then confirm the listener isn’t bound to 127.0.0.1. Make sure the firewall rule applies to the current network profile, and check for guest network or client isolation settings on the router. Even when the phone and PC show the same Wi-Fi name, network policies may keep them apart.

The browser works, but video apps on the TV still won’t load?

First, test the same proxy on the TV’s browser. If it works, check whether the video app honors the system HTTP proxy or requires a different transport. Don’t open all UDP traffic in Windows Firewall as a first step; if the app ignores the system proxy, opening ports won’t automatically route its connections.

What if the device says the proxy server refused the connection?

On the PC, confirm the core is still running and check the actual port. Common causes include swapping the HTTP and SOCKS ports, another process using the port, or the service failing to start after you saved the settings. A refused connection usually points to the listener or service status; a timeout also warrants checking the firewall and network path.

It worked yesterday, but stopped after restarting the PC?

Run ipconfig again and check whether DHCP assigned the PC a new address. Also check whether the device’s address changed and is now outside the firewall allowlist. You can reserve DHCP addresses for the PC, phone, and TV in your router to avoid configuration issues when addresses change. Then confirm the v2rayN service is running.

If v2rayNG is already running on my phone, do I still need to set a Wi-Fi proxy?

First decide whether you’re testing the phone’s own proxy or the proxy shared from the PC. To test PC sharing, stop any other proxy or VPN session on the phone to avoid stacking connections. v2rayNG and v2flyNG connect from the phone itself; they aren’t required for inbound connections to the PC over the LAN.

When you’re done: disable the listener and revoke access

A LAN proxy lets authorized devices use the outbound connection configured on the PC. Limit access even on a home network: don’t create public port mappings on the router, and don’t treat public Wi-Fi as a trusted LAN. If the listener is bound to all interfaces, remember that it may also be reachable over other network interfaces the PC connects to later.

For regular use, reserve DHCP addresses for the devices and configure Windows Firewall to allow only those devices on the ports you actually use.
If you use only the HTTP listener, there’s no need to open the unused SOCKS port. Review any existing broad allow rules as well.
To stop sharing, turn off “Allow connections from the LAN,” restart the service, and confirm the listener is bound to the local machine again.
On your phone and TV, set the Wi-Fi proxy to “None” or restore the previous setting so they don’t keep trying to connect to the old address away from home.

If you created the example firewall rule in this guide, run the command below in an elevated PowerShell window to remove it. Removing this rule won’t delete other existing program allow rules, so test the port again from another device afterward.

Remove-NetFirewallRule -DisplayName "v2rayN LAN TCP restricted"

Summary: Make shared proxy settings testable and reversible

Keep a record of the PC’s address, proxy type, actual port, and firewall rule name. If something breaks, test each layer in the same order and undo each change when you’re done. This makes troubleshooting easier than repeatedly changing subscriptions or loosening network permissions across the board.