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

Confirm the Sharing Path and Its Limits

v2rayN’s “Allow connections from the LAN” option changes the local proxy binding from loopback-only to an address available on the LAN adapter. Other devices do not control v2rayN or automatically receive the PC’s subscriptions; they simply send requests to the PC’s local address and specified port, where v2rayN processes them through the currently enabled node.

Sharing works only when four conditions are met: the PC and target device are on a reachable LAN, the v2rayN core is running, the inbound port listens on an address accessible from the LAN, and Windows Firewall allows inbound TCP traffic on that port. If any condition is missing, the device cannot connect even with correctly formatted settings.

Phones and TVs usually connect through manual HTTP proxy settings over Wi-Fi, so check v2rayN’s HTTP port first. The SOCKS port is mainly for apps that explicitly support SOCKS5 and cannot be entered into system settings that accept only an HTTP host and port. Different v2rayN versions, migrated configurations, and automatic port changes can affect the actual values; do not rely only on default ports from a guide.

• Connect the PC by Ethernet or Wi-Fi to the same home network as the target device.
• If the router enables “guest network isolation” or “wireless client isolation,” devices may be unable to reach each other even when they use the same network name.
• This shares an application-level proxy; it does not turn the PC into a gateway for every protocol.
• With an HTTP proxy, some apps may bypass the system Wi-Fi proxy. A successful browser test does not mean every app will use this path.
• Do not expose the proxy port through router port forwarding. Keep sharing limited to a trusted local network.

Enable LAN Listening in v2rayN

First select an available server in v2rayN and confirm that the PC browser can reach the target page through v2rayN. Sharing settings cannot fix a failed node; if the PC itself cannot connect, resolve subscription, node, or routing issues before opening a LAN port.

In v2rayN, go to “Settings” → “Parameter Settings” → “Basic Settings” and enable “Allow connections from the LAN.” Some 7.x interfaces place this option under core settings or system proxy settings; save the change as prompted. If the core does not restart automatically, use “Restart Service” in the main window, then check the listening state again.

10808 and 10809 are common defaults, not fixed ports used by every installation. If v2rayN shows 10811 as the HTTP port, use 10811 on both the device and firewall rule. Ports are decimal integers; do not add a protocol prefix, slash, or spaces.

1. Open v2rayN and confirm that the current node is set as the active server.
2. Go to “Settings” → “Parameter Settings” → “Basic Settings.”
3. Enable “Allow connections from the LAN” and record the SOCKS and HTTP ports.
4. Save the settings and restart the service. Check the main-window log for port-in-use errors.
5. Keep v2rayN running; do not exit the tray application while testing the device.

Find the PC’s Local Address and Verify the Listening Port

The proxy server address on the target device must be the PC’s IPv4 address on the current LAN, such as 192.168.1.23 or 10.0.0.16—not 127.0.0.1. On a phone, 127.0.0.1 refers to the phone itself; on a TV, it refers to the TV itself, so it will not point to the PC running v2rayN.

In Windows, press Win + R, enter cmd, and run ipconfig. Find the connected “Wireless LAN adapter” or “Ethernet adapter” and read its IPv4 address. Do not choose an adapter marked “Media disconnected,” or an address shown by a virtual adapter, container adapter, or temporary tunnel adapter.

After recording the address, confirm that the port is actually listening. Run the following command in a Windows terminal; if the HTTP port is not 10809, replace the port in the command with the value shown in the interface. If the local address in the output is 0.0.0.0:10809 or the PC’s LAN address followed by the port, the LAN adapter can accept connections. If it shows only 127.0.0.1:10809, listening is still restricted to the PC.

ipconfig
netstat -ano | findstr :10809
netstat -ano | findstr :10808

If the command returns no output, first check the v2rayN log for a port-in-use message such as “address already in use.” Close the program using the same port, or choose an unused port under “Settings” → “Parameter Settings.” When a port changes, update the firewall rule and device settings as well.

Configure Windows Firewall to Allow Only the Local Subnet

A LAN listening address in v2rayN does not guarantee that Windows allows inbound connections. When opening the port for the first time, Windows may show a network access prompt; select “Private networks” only. If the prompt was previously declined or never appeared, create an inbound rule manually.

Open “Windows Security” → “Firewall & network protection” → “Advanced settings” → “Inbound Rules” → “New Rule.” Choose “Port” as the rule type, TCP as the protocol, and enter the actual HTTP port under specific local ports, such as 10809. Select “Allow the connection,” enable only the “Private” profile, and name the rule “v2rayN LAN HTTP 10809.”

If you also need to share the proxy with apps that support SOCKS5, create a second TCP inbound rule for the actual SOCKS port. Do not combine ports into a broad range such as 10800–10900; allowing 10808 and 10809 individually is easier to audit and reduces coverage of unrelated services.

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

The PowerShell command above must be run in an administrator terminal and assumes an HTTP port of 10809. After creating the rule, check its name, port, profile, and remote address under “Inbound Rules.” If Windows identifies the current network as “Public,” first confirm that it is a trusted home network, then change the profile to “Private.” Do not simply extend the rule to every profile.

Enter Proxy Settings on the Phone and TV

On the phone, open the details for the current Wi-Fi network and find “Proxy” or “Advanced options.” Change the mode from “None” to “Manual.” Enter the PC’s IPv4 address, such as 192.168.1.23, as the proxy hostname, and v2rayN’s HTTP port, such as 10809, as the proxy port. Leave the bypass list empty initially, save, and reopen the browser to test.

On a TV, the option is usually under “Network” → “Current Wi-Fi” → “Proxy settings” or “Advanced settings.” Select manual proxy and enter the same PC IPv4 address and HTTP port. Some TV systems require the IP setting to remain DHCP before proxy settings can be expanded; in that case, do not change the TV’s own IP, gateway, or DNS.

If the target device already has v2rayNG or v2flyNG installed and can import the same subscription directly, routing through the PC is usually unnecessary. LAN sharing is better suited to TVs or temporary devices that cannot run a client directly but support system-wide HTTP proxies. v2rayNG uses the Xray core, while v2flyNG uses the v2fly core; when connecting directly, each device handles node selection and routing itself.

1. Make sure the PC is not sleeping and the v2rayN icon is still in the system tray.
2. Turn off mobile data on the device and keep only the Wi-Fi shared with the PC, so test traffic does not use another path.
3. After saving the manual proxy, fully close and reopen the browser.
4. Open a page that has not been cached and check whether new connections appear in the v2rayN real-time log.
5. After testing, open the target app and determine separately whether the browser and app both follow the system proxy.

Troubleshoot in Four Layers

Do not change the port, node, firewall, and device address all at once. First confirm that the device can reach the PC, then verify that the TCP port is allowed, next check whether v2rayN receives the connection, and only then inspect the node and routing. Layered testing distinguishes “cannot reach the PC at all” from “the proxy receives the request but outbound traffic fails.”

The clearest evidence is the v2rayN log. If opening a page on the device produces no log activity, the issue is usually the LAN address, wireless isolation, listening address, or firewall. If an inbound connection appears but then times out, check the active node, subscription status, routing rules, and connectivity to the target site.

You can also temporarily disable the device proxy and test whether ordinary pages load. If the network recovers, Wi-Fi and DNS are probably fine, narrowing the issue to the PC address, proxy port, or proxy outbound path. If the device still cannot connect without the proxy, fix its own network connection first.

• No log connection: check the IP, port, wireless isolation, listening address, and firewall.
• Connection appears in the log but times out: check the active node, subscription availability, and upstream route.
• Pages work but one app fails: confirm whether the app uses the system HTTP proxy.
• Stops working after a while: check PC sleep, whether v2rayN exited, and whether the DHCP address changed.
• All devices slow down at once: test the LAN signal, PC load, and node latency separately instead of changing protocol settings first.

Three Settings to Keep Stable for Long-Term Sharing

After a successful temporary test, keep the PC address, port, and running state stable for long-term use. The most reliable approach is to reserve a DHCP address for the PC in the router so the same adapter always receives the same IPv4 address. Keep a clearly named firewall rule as well, so the port’s purpose remains obvious later.

Keep the local port unchanged in v2rayN and enable launch at system startup if needed. When the PC sleeps, hibernates, or shuts down, proxy access on every other device stops immediately, so the sharing PC must remain powered on, connected, and running the core normally. Node switching and subscription updates remain centralized on the PC; devices do not need their proxy host or port changed.

1. Reserve the PC’s DHCP address in the router, for example 192.168.1.23.
2. Record the HTTP port in v2rayN, such as 10809, and avoid conflicts with other local services.
3. Keep a TCP inbound rule limited to the “Private” profile and “Local Subnet.”
4. Set the PC’s power plan so it does not sleep automatically while sharing.
5. After changing the router or subnet, recheck the PC’s IPv4 address and wireless isolation settings.