Share Your v2rayN Proxy over LAN: Set Up TVs, Tablets, and PCs

Learn how to enable LAN access in v2rayN, check its listening address and port, allow access through Windows Firewall, and configure HTTP or SOCKS proxies on other devices.

At a glance

For anyone running v2rayN on a Windows PC who wants to share its proxy with other devices at home. Find the PC’s LAN address and active proxy port, then configure each device with a supported protocol. If a connection fails, check the listening port, firewall, device isolation, and whether the app uses the proxy settings.

LAN sharing changes the inbound listener

When you enable “Allow connections from the LAN,” v2rayN can accept proxy connections from other devices. A TV or tablet still connects to the internet through the router; only apps that support proxies send their requests to this PC. Once a request reaches the PC, the core uses its routing rules to decide whether to connect directly or through the selected outbound node.

App requestLAN connectionProxy inboundRoute matchingOutbound traffic

“Set system proxy” on the host PC affects apps on that PC; it is separate from accepting requests from other devices. Sharing does not require enabling the host’s system proxy, nor does it turn the PC into a LAN gateway. The receiving device only needs the proxy address and port—there’s no need to change its default gateway or import nodes or a subscription.

127.0.0.1
IPv4 loopback address for local access only
0.0.0.0
Listen on all local IPv4 interfaces
10808
Common mixed proxy port in v2rayN 7.x

0.0.0.0 is a listening address, not the server address to enter on your TV. 10808 is not a fixed value either: check the current configuration and active listener if you changed the local port, set a separate LAN port, or use a different version.

Enable sharing and confirm the PC address and port

  1. Test the host PC first. Make sure the v2rayN core is running and the selected node works. Use a local app to open a known accessible webpage through the proxy, so an upstream connection issue isn’t mistaken for a LAN problem.
  2. Find the IPv4 address. Run ipconfig in Windows Command Prompt. Under the adapter connected to your home router, look for the IPv4 address listed under “Wireless LAN adapter Wi-Fi” or “Ethernet adapter.” This guide uses 192.168.1.23 as an example; use your own address, not the example, the default gateway, or a virtual adapter address.
  3. Enable listening. In the common v2rayN 7.x interface, open “Settings” → “Parameter settings,” then enable “Allow connections from the LAN” in the core or inbound settings. The section names and switch labels can vary between minor versions. If you set a separate LAN inbound port, note it down; otherwise, note the local proxy port used for LAN access. If the listener doesn’t update after saving, restart the client and check again.
  4. Check the listener. Use PowerShell to check the address the port is listening on. If you see only 127.0.0.1, other devices can’t connect to this entry point over IPv4. If you see 0.0.0.0 or the PC’s actual LAN IPv4 address, check the firewall next. If another process is using the port, resolve the conflict rather than changing settings only on the receiving device.
Get-NetTCPConnection -State Listen -LocalPort 10808 |
  Select-Object LocalAddress, LocalPort, OwningProcess

Replace 10808 in the command with the port you noted in the previous step. This checks the proxy inbound port, not the remote node’s server port. Even if a node uses 443, you usually shouldn’t enter 443 on the TV.

Windows Firewall: allow inbound connections from trusted devices only

Even with a listening port, Windows Firewall may block access from other devices. On a trusted home network, go to “Settings” → “Network & Internet” and confirm the current network profile is set to “Private.” Don’t switch public Wi-Fi to Private just to share a proxy, and don’t turn off the firewall entirely.

  1. Run wf.msc, then go to “Windows Defender Firewall with Advanced Security” → “Inbound Rules” → “New Rule.” Select “Port” and “TCP,” then enter the confirmed proxy port under “Specific local ports.”
  2. Select “Allow the connection” and check only “Private” for the profiles. Give the rule a descriptive name, such as “v2rayN Home Proxy TCP 10808.”
  3. Open the new rule’s “Properties” → “Scope.” Under “Remote IP address,” add the receiving device’s actual address where possible. If its address changes often, set up a DHCP reservation on your home router. You can also allow a trusted subnet, such as 192.168.1.0/24, but only if you’ve confirmed that the subnet contains trusted devices.

Set up the proxy on a TV, tablet, or PC

The receiving device’s settings determine whether to use HTTP or SOCKS5. Most Wi-Fi settings pages with a “Manual proxy” option expect an HTTP proxy. Don’t enter a SOCKS5-only port just because v2rayN supports SOCKS5. The two cards below assume 10808 is a confirmed mixed port that accepts both protocols. If you configured separate inbound ports, enter the one that matches the protocol.

Manual HTTP proxy

Use with
Manual proxy settings for a TV or tablet’s Wi-Fi, or the system proxy on another PC
Proxy host
192.168.1.23
Proxy port
10808
Authentication
Leave blank if authentication is disabled

When host and port have separate fields, enter the host without a protocol prefix or port number.

SOCKS5 app proxy

Use with
Proxy settings in apps that explicitly support SOCKS5
Proxy type
SOCKS5
Proxy host
192.168.1.23
Proxy port
10808

If the app has a separate “Resolve hostnames through proxy” option, enable it as needed for your DNS setup.

  • TVs and Android tablets: Open the details or edit page for the current Wi-Fi network, then look under “Advanced options” for “Proxy” → “Manual.” Menu names vary by device. If there’s no proxy option, check whether the app you want to use has its own proxy settings. Don’t enter the proxy address in the gateway field under IP settings.
  • Another Windows PC: Go to “Settings” → “Network & Internet” → “Proxy.” Under “Manual proxy setup,” turn on the proxy server and enter the address and port. If you only need to proxy an app that supports SOCKS5, use the app’s own settings instead.

An HTTP proxy can usually tunnel HTTPS webpages with CONNECT, but that doesn’t mean all traffic on the device will use the proxy. Video apps may ignore the system proxy, and traffic over UDP can’t be forwarded through the HTTP form described above. Test the proxy in a browser first, then test the app separately.

Test the connection and troubleshoot common issues

If you have a second Windows PC, start by running Test-NetConnection 192.168.1.23 -Port 10808. Replace the address and port with your actual values. A TcpTestSucceeded result of True only confirms that the TCP port is reachable; it doesn’t confirm that the proxy protocol matches, DNS works, or the node is available.

Why does it time out when both devices are on the same Wi-Fi?

First check the host PC’s IPv4 address and listening port, then check the remote address range in the firewall rule. Even if both devices show the same Wi-Fi name, guest network settings or client isolation may prevent them from communicating. Connect the test device to a trusted home network that allows device-to-device access, then test the port again. There’s no need to disable isolation on the guest network.

The port is reachable, so why won’t the webpage load?

Make sure the protocol selected on the receiving device matches the inbound protocol. If an app supports only HTTP but the port accepts only SOCKS5, the TCP test may still succeed. Once the protocols match, open the same webpage through the local proxy on the host PC, then check the v2rayN logs to see whether the request failed to reach the proxy, DNS resolution failed, or the outbound connection failed.

The webpage loads, but why doesn’t the video app on the TV work?

First confirm that the TV’s browser is actually using the proxy, then check whether the video app has its own network settings. If only the browser follows the Wi-Fi proxy setting, changing ports usually won’t help. An app may ignore the system proxy or rely on traffic the proxy doesn’t forward, so a webpage loading successfully doesn’t mean the app should work too.

It worked yesterday, but stopped today without any settings changes. Why?

Check whether the host PC went to sleep, v2rayN was closed, or the network changed. Then run ipconfig to see whether the address has changed. If the firewall rule allows only specific receiving-device addresses, check whether the receiving device’s address changed too. For regular use, set up DHCP reservations for the devices; for occasional use, update the settings with their current addresses.

Download V2Ray clients