v2rayN LAN Proxy Setup: Share Your PC’s Proxy with Phones and TVs

At a glance

This guide is for users whose v2rayN connection works on a PC and who want to share it with an Android phone or TV on the same router. Configure the listening address, PC’s local IP, firewall, and device proxy settings, then troubleshoot with a port test and connection logs. The examples use a Windows PC as the proxy host. Addresses and ports are illustrative; use the values configured on your PC.

1. LAN Proxy Sharing vs. System Proxy

In v2rayN, “Allow connections from the LAN” controls whether other devices can access the local proxy inbound. “System proxy” tells supported apps on the PC to use Windows proxy settings. These are separate settings. A working browser on your PC doesn’t mean your phone can reach the PC’s proxy port.

Device proxy settings PC’s local port Core routing rules Direct or proxied

When a phone sends a request through the PC, the core still chooses a direct or proxied outbound route according to its current routing rules. You’re sharing an HTTP or SOCKS proxy endpoint—not copying the PC’s entire network setup or distributing its subscription URL. The PC must stay powered on and connected to the network, with the v2rayN core running.

System proxy: Primarily affects apps on the PC that follow its system proxy settings; it doesn’t open a LAN port.
LAN connections: Let phones and TVs connect to a proxy inbound opened on the PC.
TUN mode: Routes network traffic on the PC where it’s enabled. Enabling it alone won’t turn the PC into a transparent gateway for your phone.
Limitations: Apps on the connected device must support the proxy you configure. A Wi-Fi HTTP proxy usually won’t cover every app, and it doesn’t mean game traffic over UDP is being proxied.

2. Enable LAN Connections and Check the Listening Port

First, select an available server on the PC and confirm that the connection works. Then go to “Settings” → “Parameter Settings” and find “Allow connections from the LAN.” It’s usually under Core or Basic settings; tab names can vary by version, so look for the setting itself. Enable it and save. If it doesn’t take effect right away, restart the core and check its listening status again.

Note the local proxy port shown in Parameter Settings and check whether it’s for HTTP, SOCKS, or a mixed inbound.
If your version has a separate LAN port or authentication setting, note its details. Don’t assume it uses the same port as the loopback endpoint on the PC.
Check the listening address in PowerShell. An endpoint listening only on 127.0.0.1 can’t be reached from a phone.
If another process is using the port, identify it before changing the v2rayN port, then update the device settings to match.

10808

Example mixed inbound port used in this guide

127.0.0.1

Loopback address; accessible only from this PC

0.0.0.0

Listening on all IPv4 interfaces

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

Here, 10808 is only an example; not all versions use the same default. Older configurations may use separate HTTP and SOCKS ports, or different port numbers. A mixed inbound accepts both proxy protocols on the same port, but a SOCKS-only inbound can’t be configured as an HTTP proxy. If the result shows ::, check the core’s dual-stack behavior to confirm IPv4 access. This line alone doesn’t prove that a phone can connect.

3. Find Your PC’s Local IPv4 Address

Run ipconfig in a terminal on the PC. Find the IPv4 address under the active “Wireless LAN adapter WLAN” or “Ethernet adapter” connected to your router. Don’t use an address for a TUN interface, virtual machine, disconnected network adapter, or another network.

ipconfig

IPv4 Address . . . . . . . . . . . . : 192.168.1.23
Subnet Mask . . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . . . . : 192.168.1.1

This is sample output, not a record from a live test. Set the proxy host on your phone to 192.168.1.23—not the gateway 192.168.1.1 or 127.0.0.1. On a phone, the latter refers to the phone itself. 0.0.0.0 is a listening address and shouldn’t be entered as the proxy host either.

Your PC can use Ethernet while your phone uses Wi-Fi, as long as the router allows traffic between the two networks.
Being connected to the same Wi-Fi network name doesn’t guarantee that devices can reach each other. Guest networks, wireless client isolation, and separate VLANs can all block access.
Your PC may get a new IP address after reconnecting. For ongoing use, reserve its DHCP address in your router so you don’t have to update the phone each time.

Recommended order: Confirm the address, then configure the device

Check which network adapter is active and confirm its current IPv4 address before configuring the phone proxy. If the address has changed, refreshing subscriptions or switching servers won’t fix a connection to the PC’s old address.

4. Allow Access Through the Firewall Only on Trusted Networks

If the port is listening but the device still times out, check Windows Firewall next. On a trusted home network, open “Settings” → “Network & Internet” → the properties for your current connection and check its network profile. Set it to “Private” only if the network is genuinely trusted. Don’t change a public hotspot to Private just to share a proxy.

Open “Windows Security” → “Firewall & network protection” → “Advanced settings.”
Go to “Inbound Rules” → “New Rule” → “Port,” select TCP, and enter the actual inbound port, such as 10808.
Select “Allow the connection,” check only “Private” for the network profiles, and give the rule a recognizable name.
After creating the rule, open its Properties and go to “Scope.” Limit remote IP addresses to the devices that need access or to a verified local subnet.

You can also run this equivalent example in an elevated PowerShell session. It allows TCP 10808 from the example subnet on private networks only. If your home network uses a different subnet, change it to match. This HTTP proxy test doesn’t require an additional UDP rule.

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

5. Configure the Proxy on Your Phone or TV

On most Android phones, go to “Settings” → “WLAN” or “Network & Internet” → your current Wi-Fi network → “Modify network” → “Advanced options” → “Proxy,” then select “Manual.” On some devices, the option is under an Edit button on the network details page. Enter the host and port, save, and reconnect to Wi-Fi if needed.

Manual HTTP proxy for Wi-Fi

Proxy hostname: 192.168.1.23
Proxy port: 10808
Required inbound: HTTP or mixed inbound
Format: Enter the host without a protocol prefix

Examples are for phones and TVs that support this setting. Replace the address and port with the actual values for your PC.

SOCKS5 proxy in an app

Server address: 192.168.1.23
Server port: 10808
Protocol: SOCKS5
Required inbound: SOCKS or mixed inbound

For apps that offer SOCKS5 settings only. Android’s manual Wi-Fi proxy is generally an HTTP proxy.

TV network menus vary by manufacturer. Some TVs offer proxy settings only over Wi-Fi, while some wired network menus have no proxy option. If you can’t find one, check whether the app has its own proxy settings. If neither the system nor the app lets you configure a proxy, this method won’t work for that app.

Enter the proxy host and port separately. Don’t paste 192.168.1.23:10808 into the host field.
An HTTP proxy can also tunnel HTTPS connections with CONNECT; you don’t need to install an additional certificate.
If an app offers remote DNS resolution for SOCKS5, enable it if needed. How DNS works with a Wi-Fi HTTP proxy depends on the app, so don’t assume all DNS requests go through the PC.
For testing, pause any other proxy or VPN connections on your phone to avoid routing conflicts. When you leave the Wi-Fi network or stop sharing, set the manual proxy back to “None.”

6. Troubleshoot in Order: Port, Protocol, Route

First confirm that the device can reach the PC, then check whether traffic is going through the proxy. Run the port test below from another Windows device. Don’t run it only on the PC sharing the proxy: a successful local test doesn’t prove that the firewall allows remote connections. If your phone or TV has no terminal tool, test in a browser and check the core logs on the PC at the same time.

Test-NetConnection 192.168.1.23 -Port 10808

curl.exe --proxy http://192.168.1.23:10808 --connect-timeout 5 https://example.com/

TcpTestSucceeded : True means only that the TCP port is reachable. It doesn’t confirm that the proxy protocol, outbound server, or routing is working. The second command attempts an HTTPS request through the HTTP proxy. It confirms only that this request works—not that every app on your phone will use the proxy.

The proxy works on your PC, but your phone keeps timing out?

First check whether the PC’s IPv4 address has changed, then confirm that port 10808 is listening on an address reachable from the LAN. Next check the inbound rule for the Private profile, its remote address range, and any guest network isolation on the router. Don’t change the subscription at this stage.

The port is reachable, but your browser reports a proxy error?

Check whether the phone is configured for an HTTP or SOCKS inbound. If authentication is enabled, make sure the device supports it and that you’ve entered the right credentials. Check the core logs to distinguish a protocol mismatch from an outbound proxy failure.

Your browser works, but the video app on your TV doesn’t?

First check whether the app follows the system HTTP proxy, then look for its connections in the core logs during playback. Some apps ignore proxy settings or use other transport methods. Changing the PC’s system proxy won’t force those connections through it.

Everything stops working after sharing for a while?

Check whether the PC went to sleep, the core stopped, Wi-Fi reconnected with a new IP address, or the network profile changed to Public. If you changed the port, update both the device settings and firewall rule.

If the port and protocol work but a particular destination doesn’t, check the current server and routing rules. If a rule sends traffic direct, requests won’t switch to the proxy just because they came from a phone. Check the rule against the destination domain and core logs. Avoid changing several settings at once, or you won’t know which change made a difference.

7. Wrap Up After Sharing

A LAN proxy is useful for temporary testing and a few devices on a trusted home network. For regular sharing, consider the PC’s sleep settings, its reserved IP address, and inbound firewall permissions together. If you take a laptop to another network, don’t leave the proxy open with access allowed under your home network’s trust settings.

When you’re done sharing, turn off “Allow connections from the LAN” and confirm that the setting has been saved.
Remove the manual proxy setting on your phone and TV so they don’t keep trying to use the old endpoint when the PC is off.
Delete or disable the firewall rule you created for sharing. Leave rules for other apps unchanged.
Before sharing again, check the address, port, and core logs. Don’t assume that a working setup last time means the devices can reach each other on the current network.