v2rayN Allow LAN Connections: Share Your Proxy with a TV Box or Another PC

At a glance

This guide is for using v2rayN on a Windows PC and sharing its proxy with a TV box or another computer on your home network. First confirm the proxy works locally, then enable LAN listening, check the port, restrict access in the firewall, and enter the host address on the other device. This shares an HTTP or SOCKS proxy service; it does not turn your entire home network into a proxy.

1. Requirements and how traffic flows

Make sure the node connects from the PC running v2rayN before setting up sharing. If the node is unavailable, opening the listener and firewall only gives other devices access to a proxy that cannot reach the internet properly. This guide uses Windows as the host; firewall screens differ on other desktop operating systems, so do not assume the Windows commands below will work there.

Device proxy settings LAN listener Routing rules Outbound connection

The client device must be able to reach the host's local network address. Devices connected to the same router usually can, but guest networks, wireless client isolation, and access controls between VLANs may block them. Being connected to Wi-Fi networks with the same name does not guarantee that devices can reach each other.

Keep the host running: Sleep, shutdown, quitting v2rayN, or stopping its core will make the shared proxy unavailable.
The device must support manual proxy settings: Use this setup only if its network settings let you enter an HTTP proxy, or the app itself supports HTTP or SOCKS proxies.
The host does not need System Proxy enabled: System Proxy affects apps on the host that use that setting; it is not required for remote devices to connect to the listening port.
Tun mode is not required: Sharing a manually configured proxy does not depend on Tun mode or Windows Internet Connection Sharing.

2. Enable connections from the local network

In v2rayN, open Settings → Parameter Settings and look for Allow connections from the local network. This option is usually under Basic Settings or the core-related settings; tab names may vary by version, so look for the option itself. Enable it and save. If prompted to restart the core, do so.

Note the local listening port in use and the protocols it supports. A mixed port accepts both HTTP and SOCKS requests through the same endpoint.
Enable Allow connections from the local network, save your settings, and wait for the core to restart.
Open PowerShell and check that the port is actually listening—not just that the setting is enabled.
Check the v2rayN logs. If you see errors such as a port conflict or a failed configuration load, resolve them before setting up other devices.

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

10808 is an example port used below; replace it with the actual port before running the command. If the only address shown is 127.0.0.1, the listener is available only on the host. 0.0.0.0 usually means it listens on all IPv4 interfaces. If only :: appears, test IPv4 connectivity from another device rather than assuming dual-stack behavior from this line alone.

3. Find the host address and proxy port

In PowerShell or Command Prompt on the host, run ipconfig. Find the connected Wi-Fi or Ethernet adapter and note its IPv4 address. Do not use a disconnected adapter, virtual adapter, or loopback address. The examples below assume the host is 192.168.1.20 and the home subnet is 192.168.1.0/24; these are examples, not your actual network settings.

10808

Example mixed listener port; use the value from your configuration

10809

Separate HTTP port in some older configurations; the value is not fixed

Do not enter the server port from a subscription node on the TV box. A node port belongs to the remote server; devices on your LAN need to connect to the inbound listening port on this PC. Port numbers alone do not tell you which protocol is supported: some configurations use separate SOCKS and HTTP ports, while others use a mixed listener.

Example HTTP proxy settings for a TV box

Proxy host: 192.168.1.20
Proxy port: 10808
Requirement: The host must provide an HTTP or mixed proxy on this port

Enter only the address in the host field—no http:// prefix and not the router address.

Example of a separate port in an older configuration

Proxy host: 192.168.1.20
HTTP port: 10809
Requirement: The configuration must explicitly enable this HTTP listener

If the only available listener is SOCKS, you cannot enter it directly in the system HTTP proxy field.

If the host gets its address via DHCP, it may change after reconnecting. For reliable sharing, reserve an address for the host's network adapter in your router's DHCP settings so it keeps the same address. Do not assign an arbitrary static address that might conflict with another device.

4. Allow access only from your home network in Windows Firewall

In Windows Settings → Network & Internet, open the properties for the current connection and confirm it is a trusted home network. Then set the network profile to Private. Do not change a public network to Private just to share a proxy, and do not turn off the entire firewall to troubleshoot.

Open Windows Security → Firewall & network protection → Advanced settings.
Under Inbound Rules, create a new port rule, select TCP, and enter the actual HTTP or mixed listener port.
Allow the connection, select only the Private profile, and give the rule a recognizable name.
Open the rule properties and, under Scope, restrict the remote IP addresses. Preferably enter the address of each device that needs access, or specify your trusted home subnet.

You can also create a rule in an elevated PowerShell session. The command below allows only the example home subnet to access TCP 10808 on the example host. Replace the address, subnet, and port before running it. To allow just one device, change -RemoteAddress to that device's reserved LAN address.

New-NetFirewallRule `
  -DisplayName "v2rayN LAN HTTP 10808" `
  -Direction Inbound `
  -Action Allow `
  -Protocol TCP `
  -LocalAddress 192.168.1.20 `
  -LocalPort 10808 `
  -RemoteAddress 192.168.1.0/24 `
  -Profile Private

This rule is for the HTTP proxy setup described here; it does not automatically allow UDP. Adding a narrowly scoped rule does not restrict any broader program-allow rules already in place, so check their profiles and scopes too. If security software also manages network access, review its inbound rules as well.

5. Configure the proxy on a TV box or another PC

TV box: enter the HTTP proxy host and port

A common path is Settings → Network & Internet → current Wi-Fi network → Proxy settings → Manual. Some devices require you to open Modify network or Advanced options first. Whether proxy settings are available for a wired connection depends on the device's operating system. Change only the proxy fields; do not alter the IP address, gateway, or DNS just to find the proxy setting.

Enter the host's actual LAN address as the proxy host, for example 192.168.1.20.
Enter a port confirmed to support HTTP, such as the mixed listener 10808 used in this guide.
Keep the existing bypass list for now. After saving, reopen the app you want to test; if needed, close its existing connections and try again.
First test with a browser known to use the system HTTP proxy, then try the specific video or other app.

A TV box's system proxy usually does not route all device traffic. Some apps use their own networking stack or connect over UDP or QUIC, bypassing the system HTTP proxy. If a browser works but one app does not, check whether that app supports proxies before assuming the node is down.

Another Windows PC: set up a manual proxy

Open Settings → Network & Internet → Proxy → Manual proxy setup, turn on Use a proxy server, enter the host address and HTTP port, and save. Check the app's own proxy settings too, if it has them, to make sure it is not still using an old address. Do not enter 127.0.0.1 on the client PC; that points to the client itself.

For apps that support SOCKS5: Select SOCKS5 in the app and enter a port that the host provides for SOCKS or mixed traffic.
For apps that support HTTP only: Use an HTTP or mixed listener. Changing the protocol name will not make a SOCKS-only port work as HTTP.
If the device has other proxies configured: Identify which route the test is using so that local, system, and app-level proxy settings do not override one another.

6. Test the port, protocol, and app in order

Run the two tests below on the Windows client PC. The first checks only the TCP connection; success does not mean the proxy protocol or node is working. The second sends an HTTPS request through an explicit HTTP proxy to test the rest of the path. Replace the address and port in the commands with your actual settings.

Test-NetConnection 192.168.1.20 -Port 10808

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

Check TcpTestSucceeded in the first result, then see whether the second command completes the proxy tunnel negotiation and receives an HTTP response from the destination site. The response does not have to be a success status code; it can still help distinguish an unreachable port, a proxy rejection, and an error returned by the destination. A successful page load does not prove that every app and protocol is being proxied.

The proxy works on the host, but the TV box keeps timing out?

First check that the TV box uses the host's LAN address, then make sure the host is not listening only on 127.0.0.1. Next, check the inbound rule for the Private profile, its scope, and router client isolation. If another PC is available, use Test-NetConnection to check the port and separate network connectivity issues from app issues.

The port test passes, but the browser still cannot load a page?

Check that the HTTP and SOCKS protocols match and that no other program has taken the port. Review the current node and v2rayN logs, then run a curl command that explicitly uses the HTTP proxy. If it requests authentication, check whether the listener is configured with a username and password.

Pages load, but an app on the TV box does not use the proxy?

Check whether the app has its own proxy settings and whether it honors the system HTTP proxy. System proxy settings do not route all traffic and cannot guarantee that connections opened directly by an app will use the proxy. Do not keep switching nodes instead of checking this first.

The shared proxy works, but the results differ from the host?

Check v2rayN's routing mode and routing logs. Shared traffic is still routed according to the host's core inbound and routing configuration; it does not necessarily all go through the proxy. Remote requests may not include local process information that the host can use, so process-based routing may behave differently from traffic generated on the host.

Sharing stops working after a PC restart. What should you check first?

Check in order that v2rayN and its core are running, the host's IPv4 address has not changed, the listener is still active, and the current network is still set to Private. If sharing stops only after disconnecting and reconnecting, check for a DHCP address change first, then consider reserving an address for the host.

7. Stop sharing and restore your settings

When you no longer need to share the proxy, first turn off manual proxy settings on the TV box and client PC, then disable Allow connections from the local network in v2rayN. If you reverse the order, devices that still have proxy settings enabled may temporarily lose network access, which can look like a connection problem.

Delete or disable the inbound firewall rule you created for sharing. Do not remove rules for other apps by mistake.
Check the listening address again and confirm that the endpoint is available only to the host.
After changing your home network, host adapter, or proxy port, check the address and firewall scope again.
Manage nodes, subscriptions, and routing on the host; client devices only need the proxy endpoint details they require.

The troubleshooting order for LAN sharing stays the same: confirm the host works, check that the listener is reachable, then see whether the app uses the proxy. Change one layer at a time; this usually makes problems easier to isolate than changing the node, port, and network settings all at once. For more setup basics, see Getting Started. For connection issues, see Troubleshooting.