Enable LAN Access in v2rayN: Share Your PC Proxy with Phones and TVs

At a glance

Once v2rayN on your PC can access the internet, you can share its local HTTP proxy with phones and TVs on the same trusted LAN. Four settings matter: your PC’s LAN address, the active listening port, LAN access, and the firewall’s allowed source range. This guide uses 192.168.1.20 and 10808 as examples; these are not your device’s actual address or guaranteed default port.

1. You’re sharing a proxy endpoint, not your PC’s entire network

When a phone or TV is configured to use your PC’s proxy, apps that support proxy settings connect to the PC first. The core managed by v2rayN then routes traffic directly or through a proxy according to its routing rules. The device does not need the remote node’s VMess or VLESS settings, nor a copy of your PC’s subscription. Keep the PC powered on and connected to the network, with the core running.

Device app PC proxy endpoint Core routing rules Direct or proxied Destination service

Keep these three settings distinct. The PC’s “System proxy” setting affects local apps that use the system proxy. “Allow connections from the LAN” controls whether other devices can reach the proxy listener. TUN mode is a separate way to route traffic. Sharing an HTTP proxy usually does not require TUN, and enabling the PC’s system proxy alone is not enough.

Manual proxy settings for phone Wi-Fi usually require an HTTP proxy. Don’t enter a SOCKS-only port.
An HTTP proxy can carry HTTPS requests through a CONNECT tunnel; you don’t need to install a certificate on your phone.
Some apps don’t use the Wi-Fi proxy, especially games and certain TV apps. If a web page loads, that doesn’t mean every app is using the proxy.
Mobile data won’t automatically use the proxy configured for the current Wi-Fi network. Once Wi-Fi disconnects, this shared proxy path is no longer available.

2. Find your PC’s address and HTTP listening port

First, select an available node in v2rayN and confirm that your browser can open a destination site through the proxy. Then find the address of the Ethernet or Wi-Fi adapter currently in use. On Windows, run ipconfig in a terminal. On Linux, run the command below and check the adapter connected to your router—not a loopback, container, or virtual adapter.

ip -4 address show
ip route

For example, say your PC’s address is 192.168.1.20 and your phone’s is 192.168.1.35, with both connected to the same router. Check that the router hasn’t enabled guest network or wireless client isolation: sharing a Wi-Fi name doesn’t guarantee devices can reach each other. Don’t use your public IP, default gateway, or 127.0.0.1 as the proxy host.

PC settings (example)

LAN address: 192.168.1.20
Proxy listening port: 10808
Listener protocol: HTTP or an HTTP-capable mixed listener
Firewall source: 192.168.1.0/24

Use the port and subnet configured on your device. Example values are not test results.

Phone and TV settings (example)

Proxy type: Manual
Proxy hostname: 192.168.1.20
Proxy port: 10808
Address format: Enter the IP address only, without a protocol prefix

Don’t enter http:// in the hostname field or a colon or full address in the port field.

In v2rayN, go to “Settings” → “Parameters” and find the local listening port and inbound protocol. Depending on the version, you may see separate HTTP and SOCKS ports or a combined mixed port. If the interface has a separate “LAN” port, enter the HTTP port for that listener on your device. This guide doesn’t assume a default value for any particular version.

3. Enable LAN access and verify the active listener

In v2rayN, go to “Settings” → “Parameters” and find “Allow connections from the LAN” or an equivalent LAN access option.
Enable the option, check the HTTP or mixed listening port, and save your settings. The option name and location may vary by version.
Wait for the client to reload the core. If the setting doesn’t take effect, use the client’s restart-core option or quit and relaunch the client.
Check the logs for errors such as “address already in use” or “bind failed,” then check the listening status in your operating system.

On Linux, run the following command with the example port. In ss output, 127.0.0.1:10808 accepts IPv4 connections only from the same machine; 0.0.0.0:10808 listens on all local IPv4 interfaces; and 192.168.1.20:10808 binds to that adapter’s address. If you see an IPv6 wildcard listener, test IPv4 separately—one line of output doesn’t confirm that both address families are reachable.

ss -lntp 'sport = :10808'

On Windows, use PowerShell to check the listening address and owning process. If your port isn’t 10808, change the number in the command first. The listener may be a core launched by v2rayN, rather than the client interface itself.

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

4. Allow TCP traffic from trusted LAN devices only

Confirm that the network is trusted, then set your current Windows home network to “Private.” Don’t mark a public hotspot as private just to share a proxy. In “Windows Security” → “Firewall & network protection” → “Advanced settings,” create an inbound rule for TCP on the actual proxy port, and restrict the remote IP addresses in the scope settings. An HTTP proxy listener usually needs only TCP; don’t open UDP on the same port unnecessarily.

Rule setting	Example value	What to check
Direction and action	Inbound; allow the connection	Don’t turn off the entire firewall
Protocol and local port	TCP，10808	Match the active HTTP listener
Remote address	192.168.1.0/24	Replace with your trusted subnet
Network profile	Private	Don’t enable this rule on public networks

You can create a rule with the same scope in an elevated PowerShell session. Run the example as-is only if your local port and subnet match. To allow just one phone, narrow the remote address to that phone’s reserved LAN address.

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

If you use UFW on Linux, add a rule restricted to the allowed source. Don’t copy commands for multiple firewall managers; first check whether your distribution uses UFW, firewalld, or another tool. The example below applies only to UFW.

sudo ufw allow from 192.168.1.0/24 to any port 10808 proto tcp
sudo ufw status numbered

Troubleshooting: Narrow down the cause after confirming the listener

If the PC is listening on its LAN address but another device can’t connect to the TCP port, check the firewall and router isolation first. Don’t keep changing subscription nodes; outbound routing hasn’t come into play yet.

5. Configure the proxy on your phone or TV

Android phones: Change the current Wi-Fi settings, not mobile data

Go to “Settings” → “WLAN” or “Wi-Fi,” then open the details or edit screen for the connected network.
Expand “Advanced options” and change “Proxy” from “None” to “Manual.” The menu names vary by manufacturer.
Enter 192.168.1.20 as the proxy hostname and 10808 as the proxy port. Save the settings, then open a destination site in your browser.
For the initial test, leave the proxy bypass list empty so the destination domain isn’t accidentally excluded. Once it works, add local addresses if needed.

Don’t rely on the Wi-Fi icon to tell you whether the proxy works. Some systems use a different route for their connectivity check and may show a connection warning even when the browser works. Test a regular website, your destination site, and the apps you actually use. If the browser works but an app doesn’t, check whether that app supports the system HTTP proxy.

TVs: Check whether the system has a proxy setting

Some Android TVs let you configure a proxy under “Settings” → “Network & Internet” → “Current network” → “Advanced options.” On other models, you may need to edit or reconnect to the network before the option appears. Enter the hostname and port as you would on a phone. Wired network settings may be separate from Wi-Fi, so check again after changing connection type.

Change only the proxy fields. Don’t alter the static IP, gateway, or DNS just to find the proxy setting.
If the TV has no system proxy setting and the app has no proxy option of its own, this method can’t force that app to use the proxy.
Sharing stops if the PC sleeps, the core exits, or the network changes. A TV with the old proxy settings will also lose its connection.

6. Test in two steps: check port reachability, then proxy egress

The most useful test comes from another device on the same LAN, not from the PC running the proxy. On another computer with a command line, test the TCP connection first, then use curl with the HTTP proxy specified explicitly. The address and port below are still examples.

Test-NetConnection 192.168.1.20 -Port 10808
curl.exe -I --connect-timeout 5 --max-time 15 --proxy http://192.168.1.20:10808 https://example.com/

The first command is for Windows PowerShell. On Linux, replace curl.exe with curl in the second command. That command specifies the proxy explicitly, so it doesn’t rely on browser or system proxy settings. The 5-second connection timeout and 15-second overall timeout are test parameters, not measured network performance.

Test result	What it usually means	Next step
TCP test fails	The listener isn’t reachable	Check the IP, listener, firewall, and network isolation
TCP succeeds, but the proxy request fails	The port is reachable, but the protocol or outbound connection has an issue	Check the HTTP port and review the core logs
Response 407	The proxy requires authentication	Check whether inbound authentication is configured
curl succeeds, but the TV app fails	The app may not use the system proxy	Check whether the app supports its own proxy settings

An HTTP response from the destination site usually means the proxy request succeeded, but it doesn’t prove that all traffic is using a remote node. Routing rules may send the test domain directly. To confirm where the destination traffic went, check the core access logs for the destination domain and outbound tag. Log details depend on the core and log level in use.

7. Common proxy-sharing issues and how to stop sharing

The PC works, but the phone keeps timing out. What should I check first?

First, confirm that the phone is using the PC’s current LAN IP, not 127.0.0.1. Then check whether the proxy listens only on the loopback address and whether the phone is on a guest Wi-Fi network. Check in this order: address, listener, source rules, and network isolation. Don’t start by changing node protocols.

It stopped working after restarting the router, but the port hasn’t changed. Why?

The PC’s DHCP address may have changed. Check the adapter address again and update the proxy hostname on your devices. For long-term sharing, reserve a DHCP address for the PC in your router. If the firewall allows only one phone, account for changes to that phone’s address too.

Do I also need to run v2rayNG on my phone?

If you’re using the Wi-Fi HTTP proxy to share your PC’s connection, you don’t need to start a separate proxy connection on your phone. To use the phone independently when away from the PC, first set the Wi-Fi proxy to “None,” then configure v2rayNG or v2flyNG to avoid conflicting routes.

How do I stop sharing completely without affecting the PC?

First set the proxy on your phone and TV back to “None.” Then disable LAN access in v2rayN and reload the core. Delete or disable the inbound firewall rule you added for sharing, and check that the listener is bound to the local address again. Keep the PC’s system proxy enabled if you still need it.

For long-term independent connections, configuring a compatible client directly on each device is usually easier to maintain. v2rayNG for Android uses the Xray core, while v2flyNG uses the v2fly core. Protocol and configuration support depends on the specific client and core. LAN sharing works well when the PC is already running reliably and the device app supports HTTP proxies; it is not a transparent gateway for all traffic.