v2rayN Allow LAN Connections: Share Your Proxy with Phones and TVs

Quick overview

This guide is for users who already run v2rayN successfully on a Windows PC and want to temporarily share a proxy with an Android phone or TV on the same home network. You’ll learn how to enable LAN listening, distinguish SOCKS from HTTP ports, limit firewall access, and use logs to identify where a connection stops.

How LAN proxy sharing works

After you enable “Allow connections from the LAN” in v2rayN, the computer accepts proxy requests from other devices on the same network instead of only from the local machine. Phones and TVs do not read the computer’s subscription directly; they send requests to the computer’s HTTP or SOCKS inbound port, where the Xray or v2fly core currently running in v2rayN processes them.

This setting does not turn the entire computer into a router or automatically change other devices’ network settings. Each connected device must still be configured with the proxy server address and port. v2rayN must remain running, with an available node selected; sleep mode, a Wi-Fi change, or a new LAN address can interrupt sharing.

Device sends requestConnects to computer portv2rayN receives itRouting rule matchNode proxy outbound

For a common configuration, v2rayN uses 10808 for SOCKS and 10809 for HTTP. Different versions, migrated settings, or manual changes may use different ports, so always follow the values shown under “Settings” → “Parameter Settings” rather than copying this example.

10808

Example SOCKS port in this guide

10809

Example HTTP port in this guide

/24

Common home LAN subnet mask

Enable LAN listening in v2rayN

Before you begin, connect to a node on the computer and confirm that the browser can reach the target page. This separates an unavailable node from a failed LAN connection. The steps below use the v2rayN 7.x interface; earlier versions may use slightly different menu labels, but you still need to verify the listening switch, address, and inbound ports.

Open Parameter Settings: In the v2rayN main window, go to “Settings” → “Parameter Settings”. If the app is minimized to the system tray, double-click its tray icon to restore the main window first.
Find the basic settings: Open the page for local listening, ports, or core settings, then confirm the local SOCKS and HTTP ports. This guide uses 10808 and 10809 as examples.
Enable LAN connections: Check “Allow connections from the LAN”. This usually changes inbound listening from the local-only address 127.0.0.1 to 0.0.0.0, allowing connections through the computer’s network interfaces.
Save and restart the core: Save the settings. If the status bar does not show that the core has started again, close and reopen v2rayN, or select the current node again so inbound listening is created with the new configuration.
Note the computer’s address: Run ipconfig in Windows Terminal and find the IPv4 address for the active Wi-Fi or Ethernet adapter, such as 192.168.1.20.

The address entered on a phone or TV must be the computer’s current LAN IPv4 address, not 127.0.0.1. The latter always means “this device itself”: entered on a phone, it points to the phone rather than the computer running v2rayN.

Windows IP Configuration Example

Wireless LAN adapter Wi-Fi:
  IPv4 Address . . . . . . . . . . : 192.168.1.20
  Subnet Mask . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . : 192.168.1.1

Set the Windows Firewall access scope

Having v2rayN listen on a LAN address does not mean Windows will allow other devices to connect. When the firewall prompt appears for the first time, selecting “Private networks” is usually sufficient. If the prompt was previously denied or does not appear, check inbound rules under “Windows Security” → “Firewall & network protection” → “Advanced settings”.

Set your home Wi-Fi network to Private in Windows. Public network settings are intended for untrusted environments such as cafés and hotels, so do not open proxy ports there for convenience. Limit the rule to the v2rayN program or its ports, and restrict remote addresses to your home subnet.

Rule item	HTTP sharing example	SOCKS sharing example
Protocol	TCP	TCP; evaluate UDP only if SOCKS UDP is specifically required
Local port	`10809`	`10808`
Network profile	Private	Private
Remote address	`192.168.1.0/24`	`192.168.1.0/24`
Action	Allow the connection	Allow the connection

If your home router uses 192.168.50.x, the remote address should be 192.168.50.0/24, not 192.168.1.0/24. Use the computer’s IPv4 address and subnet mask to identify the subnet: with a 255.255.255.0 mask, the first three sections usually match.

Connection parameter checklist

Computer LAN address: 192.168.1.20
HTTP proxy port: 10809
SOCKS5 proxy port: 10808
Allowed source subnet: 192.168.1.0/24
Windows network type: Private network

Conclusion: narrow the access scope before testing

Open the required ports only on Private networks and for your current home subnet. This enables sharing while preventing unnecessary proxy requests when the computer joins another network.

Configure the proxy on Android phones and TVs

Most Android devices let you configure an HTTP proxy in the advanced settings for the current Wi-Fi network. Menu names vary by system version; a common path is “Settings” → “Network & internet” → “Internet” → current Wi-Fi → Edit network → “Advanced options” → “Proxy” → “Manual”. Enter the computer’s address, such as 192.168.1.20, as the proxy hostname, and v2rayN’s HTTP port, such as 10809, as the port.

TVs usually offer a manual proxy option in the advanced settings for the current network, with the same configuration. If the TV provides only “Proxy server” and “Proxy port”, use the HTTP port rather than the SOCKS port. After saving, disconnect and reconnect to Wi-Fi once so apps can establish fresh connections.

Manual Android Wi-Fi proxy

Proxy type: Manual HTTP
Hostname: 192.168.1.20
Port: 10809
Bypass addresses: localhost, 127.0.0.1

Replace the hostname with the computer’s current LAN IPv4 address.

Apps that support SOCKS5

Proxy type: SOCKS5
Server: 192.168.1.20
Port: 10808
Authentication: Match local inbound settings

Use these parameters only with apps that explicitly support SOCKS5.

A manual HTTP proxy configured for Wi-Fi does not guarantee coverage for all device traffic. Some apps follow the system proxy, some use their own networking stack, and some TV apps proxy only web requests. HTTP proxies mainly carry TCP requests; features that depend on UDP will not be forwarded automatically just because an HTTP port is configured.

First, open a regular webpage in the device browser to confirm that basic HTTP and HTTPS requests can pass through.
Then test the app you actually plan to use; do not rely on the Wi-Fi icon alone to confirm that the proxy is working.
If an Android device needs to handle more app traffic independently and continuously, use v2rayNG on the device and import a subscription from a compliant source instead of relying on computer sharing.
If the TV has no SOCKS5 setting, do not enter 10808 as the HTTP proxy port; use the HTTP port shown in v2rayN.

Check each link in the chain when a connection fails

During troubleshooting, avoid changing nodes repeatedly or modifying several settings at once. First check whether the phone can reach the computer’s port, then confirm that v2rayN received the request, and finally check node outbound connectivity. This quickly identifies whether the problem is Wi-Fi isolation, the firewall, local listening, or the remote node.

The phone still says it cannot connect after entering the settings?

First confirm that the phone and computer are on the same Wi-Fi, then compare the first three address sections. For example, 192.168.1.35 and 192.168.1.20 are usually on the same subnet in a /24 network. Guest Wi-Fi or AP isolation on the router may still prevent devices from reaching each other.

The port is allowed, but the v2rayN log shows no requests?

Go back to “Settings” → “Parameter Settings” and confirm that “Allow connections from the LAN” was saved, then restart the core. Check that the device is using the computer’s IPv4 address, not the default gateway or 127.0.0.1.

The browser works, but the TV app still fails?

This usually means the LAN path and HTTP port work, but the target app does not follow the system proxy or uses traffic that an HTTP proxy cannot handle. Check that the TV’s network settings were actually saved, then cross-check with another app that follows the system proxy.

Did the old address stop working after restarting the router?

The computer may have received a new address through DHCP. Run ipconfig again to find its IPv4 address, then update the proxy hostname on the phone and TV. For long-term use, reserve a DHCP address for the computer on the router.

Can sharing continue if the computer does not use a system proxy?

Yes, as long as the v2rayN core is running and the LAN inbound listener remains active, remote devices can continue connecting. The computer’s “system proxy” mainly controls whether apps that follow that setting use a proxy; it does not turn off v2rayN inbound listening.

When the log shows a connection from the phone or TV’s LAN address, the request has reached v2rayN. If a timeout follows, check the current node, subscription status, and routing rules. If no corresponding entry appears at all, continue checking the listening address, firewall, and router device-isolation settings.

Verify on the computer that the current node works normally.
Confirm that v2rayN inbound listening allows LAN connections.
Confirm that the phone and computer are on the same LAN and can reach each other.
Confirm that Windows Firewall allows the correct ports only on Private networks.
Check whether the v2rayN log shows the connected device’s LAN address.
Finally, determine whether the target app follows the HTTP or SOCKS5 proxy.

Security boundaries when sharing with other devices

A LAN proxy port provides devices on the network with a usable outbound path. Without additional authentication on the local inbound, any device on the same subnet that can reach the computer’s port may be able to use it. Limit sharing to your own controlled home network, and never leave it open on public Wi-Fi.

When sharing is no longer needed, disable “Allow connections from the LAN” and remove or disable the corresponding Windows Firewall inbound rule. Before moving the computer from your home network to an office network or public hotspot, also check the network profile and listening state so home-network rules are not carried over.

Conclusion: open shared ports only when needed

For temporary home use, allow access on Private networks and restrict the source subnet. Record the port and address after connecting devices, then disable listening and the allow rule when finished.

Do not forward 10808 or 10809 to external networks through the router.
Do not share your home proxy address and port with devices outside the same controlled network.
Reserve a stable DHCP address for the computer to avoid confusion when its address changes.
Review the v2rayN log regularly and watch for unfamiliar LAN source addresses.
When sharing is over, restore local-only listening and disable the corresponding firewall rule.

The complete chain is: v2rayN runs normally on the computer, LAN listening is enabled, the firewall allows the correct ports from the current home subnet, and the phone or TV uses the computer’s IPv4 address. Once all four conditions are met, determine the actual coverage based on whether the specific app follows proxy settings.