At a glance

Already using v2rayN on Windows and want your Android phone or TV to use the same proxy? Enable proxy listening on your PC, then enter its local IPv4 address and an HTTP-capable listening port on the other device. This guide covers example settings, a narrowly scoped firewall rule, and how to tell a blocked port from an app that ignores the proxy.

What LAN sharing actually does

You’re sharing your PC’s proxy endpoint—not a subscription link or your PC as the phone’s or TV’s default gateway. Remote devices only need the endpoint address and port; the PC handles node selection and routing. The Windows system proxy setting only affects apps on the PC that honor it. It isn’t required for LAN sharing, and you don’t need to enable TUN.

Device appLAN connectionProxy inbound on PCRouting rulesSelected outbound

A phone’s manual Wi-Fi proxy setting usually affects only apps that read it. A browser loading a page doesn’t mean a TV player, game, or every in-app connection will use the PC. Test first with an app known to support HTTP proxies, then check the target app separately.

Enable v2rayN listening and find your PC’s address

  1. Make sure the PC works first. Select a working node, confirm the core is running, and check that the PC can reach a test website using the expected route. That way, if the phone test fails, you won’t have to troubleshoot your subscription, node, and LAN connection all at once.
  2. Enable LAN connections. In the v2rayN 7.x Windows interface, open Settings → Parameter Settings, then look for “Allow connections from the LAN” under “Core: Basic Settings” or the local listening options. Section and field names may vary slightly between minor versions. Save your changes and restart the core if the listener doesn’t update. Check the logs for port binding errors.
  3. Check the inbound proxy type. If your current setup shows a mixed port, you can use it for your phone’s HTTP proxy. If SOCKS and HTTP ports are listed separately, enter the HTTP port in the manual Wi-Fi proxy settings. If a separate LAN listening port is configured, use that port—not the PC’s loopback port.
  4. Find the active network adapter’s address. Run ipconfig on your PC and find the “IPv4 Address” under the Wi-Fi or Ethernet adapter connected to your home router. Don’t use the default gateway or a virtual adapter’s address. On your phone, 127.0.0.1 points to the phone itself, not your PC.

For example, if your PC’s address is 192.168.1.23 and its mixed port is 10808, enter those values on the device. If the HTTP inbound port in your setup is 10809, use 10809 instead. These values illustrate which fields to use; they aren’t defaults for every version.

You can use PowerShell on your PC to check whether an example port is listening; replace the number in the command if your port differs. A listener bound only to 127.0.0.1 can’t accept IPv4 connections from other devices. If you see your PC’s network address or 0.0.0.0, the listener covers LAN addresses, but you’ll still need to check the firewall and test from the device.

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

Proxy settings on Android phones and TVs

First, connect your phone and TV to a home network that can reach your PC. It’s fine to connect the PC over Ethernet and the phone over Wi-Fi, as long as the router allows devices to communicate with each other. On Android, open the current Wi-Fi network’s settings—usually Settings → Network & internet → Internet—expand the advanced options, and set Proxy to Manual. On a TV, look for a similar option in the current network’s advanced settings; some models don’t offer one.

Example: Android phone

Proxy type
Manual
Proxy hostname
192.168.1.23
Proxy port
10808 (example mixed port)
Bypass proxy for
Leave blank for the initial test

Enter only the address as the hostname—no protocol prefix and no port.

Example: TV with manual proxy support

Proxy type
HTTP or Manual Proxy
Server
192.168.1.23
Port
10808 (same mixed endpoint)
IP settings
Keep the existing settings

Don’t enter the proxy host in the gateway or DNS fields.

Test the connection with a web page

After saving, open a regular HTTPS page in a browser that supports proxies. Check the core logs on your PC too, if your current setup records inbound requests. If the browser’s request reaches the PC but the target app’s doesn’t, first check whether that app uses the Wi-Fi proxy. Don’t broaden the firewall rules as a first step.

Windows Firewall: limit inbound access

Enable sharing only on a trusted home network. In Windows network properties, confirm the current connection uses the “Private” profile, then open “Windows Defender Firewall with Advanced Security.” You can also launch it with wf.msc. Don’t switch a public network to Private for testing or turn off the firewall.

  1. Under Inbound Rules, check for existing broad allow rules that cover the core or port. Adding a narrowly scoped rule won’t restrict existing rules; review and adjust any broad rules as needed.
  2. Choose New Rule → Custom. On the Protocol and Ports page, select TCP and limit the local port to the verified HTTP or mixed port, such as 10808. This is the PC’s local port, not the source port used by the phone.
  3. On the Scope page, limit remote IP addresses to the approved devices, such as the phone at 192.168.1.41 and the TV at 192.168.1.42. Choose Allow the connection, select only the Private profile, and give the rule a descriptive name.
  4. If the router assigns device addresses dynamically, set up DHCP reservations for the approved devices and the proxy PC. This helps keep the firewall rules and proxy address valid after reconnecting. When you’re done sharing, set the device proxy to None, then disable LAN listening and the dedicated inbound rule.

Troubleshooting connection problems

Did web pages start timing out as soon as you saved the proxy settings?

First compare the address entered on the phone with your PC’s current IPv4 address. Then check the listening port and make sure the firewall rule includes the phone’s source IP. If there’s another approved Windows PC on the same home network, run Test-NetConnection 192.168.1.23 -Port 10808 from it. If TCP fails, check the listener, firewall, and network isolation. A successful TCP test only confirms the port is reachable; it doesn’t prove the HTTP proxy or outbound connection works.

Both devices are on the same router. Why can’t they connect?

Make sure the phone isn’t on guest Wi-Fi and the TV isn’t on an isolated device network. Some routers block communication between clients even when their addresses look similar. Connect approved devices to a trusted home network that allows them to communicate; don’t disable guest network isolation just to test.

The TV browser works, but the media player doesn’t. Why?

Check whether the player has its own HTTP proxy settings. If it doesn’t, don’t assume it follows the TV’s network proxy. If the PC logs show requests from the player, check whether their domains match the expected routing rules and whether the selected outbound works. These are different issues; changing ports at random won’t help.

Why does the phone lose internet when the PC sleeps or reconnects to Wi-Fi?

When the PC sleeps, the phone’s saved manual proxy still points to it. Set the phone’s proxy to None to restore a direct connection. Once the PC wakes, check its network address and listening status again. If the address changed, update the proxy settings on your devices or reserve a fixed lease for the PC in your home router.