Allow LAN Connections in v2rayN: Share Your Proxy with Phones, TVs, and Other PCs

How LAN Proxy Sharing Works and When to Use It

LAN sharing does not copy your subscription to other devices. Instead, those devices connect to a proxy inbound on your PC. The core managed by v2rayN receives each request, then routes it directly or through a proxy according to the PC's routing rules. The PC remains connected to the remote server; phones and TVs generally only need the host address and port, not node settings such as VMess or VLESS.

Enabling “Allow connections from the LAN” only changes which interfaces accept inbound connections. It does not configure other devices or route all their traffic through the PC. Android's manual Wi-Fi proxy generally works with apps that honor the system HTTP proxy; games, apps with their own network stack, and some TV apps may ignore it.

• Works well for: Browsing, desktop apps that support HTTP or SOCKS5, and apps that honor the Wi-Fi proxy setting.
• Check separately: Video apps, games, UDP traffic, and how each app handles DNS lookups.
• For continuous access: Keep the PC on and reachable, with the v2rayN core running. Sharing stops when the PC goes to sleep.

Step 1: Find the Host's IPv4 Address and Inbound Port

This guide uses a Windows host, with 192.168.1.20 as the example IP and 10808 as the example port. These values illustrate what to enter; they are not defaults for every PC. First, confirm the active node can reach the destination site from the host, then open a terminal and run:

ipconfig

Find the active “Wireless LAN adapter” or “Ethernet adapter” and note its IPv4 address and default gateway. Don't use a virtual adapter, a disconnected adapter, or a loopback address. Enter the PC's LAN IPv4 address on the client—not the router's gateway, the node server's address, or 127.0.0.1. On a phone, that last address points back to the phone itself.

1. In v2rayN, open “Settings” → “Parameter Settings” and find the local listening ports and “Allow connections from the LAN.” Group names may differ between versions; follow the labels in your version.
2. Note the inbound port that supports HTTP. A mixed port usually accepts both HTTP and SOCKS requests. If the ports are listed separately, record each one and don't interchange them.
3. Enable the LAN connections option and save. Restart the core if prompted. If you're not sure the change took effect, exit and reopen v2rayN.
4. Check that a server is active and the routing rules are correct. The system proxy switch on the host is not required for remote devices to connect, but the core's inbound listener must be running.

Step 2: Check the Listener and Limit Firewall Access

First verify that the service is listening, then check the firewall. In PowerShell, run the command below using the example port. No output usually means the core isn't running, the port doesn't match, or another process occupied the port at startup.

Get-NetTCPConnection -State Listen -LocalPort 10808 |
  Select-Object LocalAddress, LocalPort, OwningProcess

Only share on a trusted home or office network. In Windows, check the network profile under “Settings” → “Network & Internet” → your current connection's properties. Don't switch a public hotspot to a private network just to enable sharing. The rule below requires an elevated PowerShell session and allows TCP 10808 from the local subnet on private networks only:

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

This rule allows traffic by port; it doesn't bind access to a specific program. On PCs with multiple network adapters, LocalSubnet may include several directly connected subnets. For tighter access, set the source to a device's reserved IP or a confirmed subnet, such as 192.168.1.0/24. Also review any existing allow rules with overly broad scopes—a new, narrower rule won't restrict them.

Step 3: Configure Phones, TVs, and Other PCs

The client device must be able to reach the host, and vice versa. Being on the same Wi-Fi network name doesn't guarantee this: guest networks and wireless client isolation can block devices from communicating. The two setup examples below use the same host; choose a protocol that matches the inbound.

1. Android phones: Open “Settings” → “WLAN” or “Network & Internet” → edit the current Wi-Fi network. Expand the advanced options, set the proxy to “Manual,” enter the hostname and port, then save. Menu labels vary slightly between Android versions.
2. TVs: Check whether the current network's advanced settings offer an HTTP proxy option. Some devices only show it after you edit the network configuration. If the system has no proxy setting, check whether the target app supports its own proxy configuration.
3. Another Windows PC: Open “Settings” → “Network & Internet” → “Proxy” → “Manual proxy setup,” then enter the address and port. During testing, check the exceptions list to make sure the destination domain isn't excluded.
4. App-specific settings: In browsers and download tools that support custom proxies, choose HTTP or SOCKS5 in the app's own settings. An app's proxy configuration may override the system settings.

After saving, test with a browser first; don't use a game or video app as your only test. The Wi-Fi proxy usually applies only to that Wi-Fi network, so check the settings again after switching networks. If v2rayNG or v2flyNG is also running on the phone, pause it during the initial test to avoid confusion from multiple layers of network routing.

Step 4: Use Two Tests to Pinpoint the Host or Client

Run the first test on another Windows PC to check whether the TCP port is reachable. Don't rely on ping alone: a device may block ICMP replies even when the TCP proxy port works.

Test-NetConnection 192.168.1.20 -Port 10808

TcpTestSucceeded : True only means a TCP connection was established; it doesn't confirm that the proxy protocol or remote outbound connection works. The second test explicitly uses the HTTP proxy to access an HTTPS site, avoiding interference from system proxy settings:

curl.exe -I --connect-timeout 10 --max-time 20 --proxy http://192.168.1.20:10808 https://example.com/

• TCP test fails: Check the host IP, core listener, Windows Firewall, third-party security software, and client isolation on the router. If the error says the connection was refused, check the listening port first.
• TCP succeeds but the HTTP test fails: Confirm that the port supports HTTP and whether authentication is required. Check the v2rayN logs for handshake or outbound errors.
• The command gets a response from the destination, but the app fails: Check whether the app honors the system proxy, has proxy exceptions configured, or requires UDP.
• You see a message that the tunnel was established: Keep checking the subsequent TLS handshake and destination response. A single line confirming the tunnel doesn't mean the site loaded successfully.

To test SOCKS5, first confirm that the port supports the protocol, then run the command below. socks5h sends the destination hostname to the proxy for resolution, which helps distinguish local DNS issues from proxy-side DNS issues. How the host ultimately handles DNS still depends on the core's DNS and routing settings.

curl.exe -I --connect-timeout 10 --max-time 20 --proxy socks5h://192.168.1.20:10808 https://example.com/

Common Issue: Why Does the Browser Work but Other Apps Don't Use the Proxy?

When You're Done: Restore Client Settings and Close Access

A LAN proxy port adds a new network-accessible service. While sharing is enabled, other devices use the host's outbound connection and bandwidth, and may consume traffic from the same service plan. Without inbound authentication, other devices within reach may also use the port, so don't leave it open on an untrusted network.

• Don't set up public port forwarding: Sharing at home doesn't require forwarding port 10808 from your router to the internet or setting the PC as a DMZ host.
• When you no longer need sharing: Turn off “Allow connections from the LAN,” restart the core, and check that it listens only on local interfaces again.
• Restore client settings: Set the manual proxy back to “None” or restore the previous setting on phones, TVs, and other PCs. Otherwise, clients may keep trying to reach an unavailable proxy after the host shuts down.
• Clean up firewall settings: Delete the rule created specifically for this sharing setup. Restore any changes you made to other security software as well.

Delete the example firewall rule with the command below. Remove only the rule you created for this setup with the matching name; don't bulk-delete existing system rules.

Remove-NetFirewallRule -DisplayName "v2rayN LAN TCP 10808"