Understand the LAN proxy path first
A shared LAN proxy does not copy a subscription to your TV or game console, nor does it make the router take over traffic automatically. The path is straightforward: v2rayN connects to a remote server on the computer while opening an HTTP or SOCKS listening port locally. Other devices on the same LAN use the computer’s LAN address as the proxy server and send requests to that port.
For example, suppose the computer’s address on your home network is 192.168.1.20, and v2rayN shows 10809 as its HTTP proxy port. Enter 192.168.1.20 as the proxy server on the TV and 10809 as the port. The port here is only an example; always use the value currently shown by the client.
This path has at least four layers: the device proxy settings, the wired or wireless LAN, the computer’s firewall, and v2rayN’s listening port. If any layer refuses the connection, the TV will usually report only “No internet connection” or “The proxy server is not responding.” Do not keep switching nodes at random. First confirm that the connection reaches the computer, then check whether the proxy can access the external network.
Also distinguish between “the proxy connection works” and “all application traffic goes through the proxy.” A device’s system HTTP proxy mainly handles TCP requests from apps that support that setting. Some apps ignore the system proxy, while real-time games may use UDP or custom connection methods. A web test can therefore succeed while a particular app connects directly or fails to establish a session. LAN sharing is suitable for temporary downloads, account sign-ins, web access, and apps that support the system proxy; it is not the same as router-level transparent forwarding.
Open the LAN listener in v2rayN
First make sure v2rayN works normally on the computer itself. Update the subscription, select an available server, start the proxy, and complete one access test in the computer’s browser. If the computer is not connected, opening a LAN port will not improve the result.
Confirm the switch and port
- Open v2rayN’s settings and find the local listener or basic settings section.
- Enable “Allow connections from the LAN” or an option with the same meaning. The wording and menu location may vary slightly between versions.
- Note the current HTTP, SOCKS, or mixed proxy port. TVs and game consoles usually work best with the HTTP port.
- Save the settings. If the client asks you to restart the core, follow the prompt; otherwise, stop and restart the proxy manually once.
- Keep v2rayN running. Do not let the computer sleep, disconnect from the network, or switch to another LAN.
When only local connections are allowed, the listener is usually bound to the loopback address 127.0.0.1. After LAN access is enabled, it should listen on the LAN interface as well, commonly appearing as 0.0.0.0 or the computer’s specific private address. 0.0.0.0 means the program accepts connections on multiple network interfaces on the computer; it is not the proxy address that other devices should use. Other devices still need the computer’s actual 192.168.x.x, 10.x.x.x, or equivalent private address.
Find the computer’s LAN address
Run this in Windows Terminal:
ipconfigFind the wireless or Ethernet adapter currently in use and read its IPv4 address. Do not choose a disconnected adapter, virtual adapter, loopback address, or remote server address.
On macOS or Linux, check the address for the active connection in the system network settings, or run this in a terminal:
ip addrA computer may be connected to Ethernet, Wi-Fi, and virtual networks at the same time. Choose the interface on the same subnet as the TV or game console. For example, if the TV is 192.168.1.46 and the gateway is 192.168.1.1, the computer should normally use an address on the 192.168.1.x subnet.
Allow the proxy port only on the home network
Even after the client starts listening, the operating system firewall may block other devices. When LAN access is enabled for the first time, authorize network access only for trusted home or private networks if the system prompts you. Do not keep the proxy port open to the same network when connected to public Wi-Fi in a café or hotel.
Windows checks
First confirm that the current network profile is set to “Private.” Then check v2rayN and its core process in the firewall’s allowed-apps list, or create an inbound rule that allows only the TCP port used by the proxy. Limit the rule to the local subnet; do not allow every source.
You can check locally whether the port is listening. Replace the port in the command below with the value currently shown by v2rayN:
netstat -ano | findstr :10809If the result shows only 127.0.0.1:10809, the program still accepts local connections only. An entry such as 0.0.0.0:10809, [::]:10809, or the computer’s LAN address indicates the basic conditions for access from other devices are in place.
macOS and Linux checks
When the macOS application firewall is enabled, allow v2rayN to accept incoming connections. On Linux, allow the corresponding TCP port with the firewall tool in use, and restrict the source to the home LAN subnet. Use the command below to inspect the listening state:
ss -lntDo not leave the entire firewall disabled just because a test failed. A safer approach is to create a narrowly scoped port rule: choose TCP, enter only the port currently used by the client, and allow only the local subnet as the source. Delete the temporary test rule after troubleshooting.
Set up a manual proxy on the TV or game console
Make sure the computer and target device are connected to the same home router. If one uses the primary Wi-Fi and the other uses guest Wi-Fi, the router may isolate them even when the network names look similar. Then open the device’s network settings and find “Proxy,” “Manual proxy,” or “HTTP proxy.”
- Choose manual proxy mode; do not select an automatic configuration script.
- Enter the computer’s LAN IPv4 address as the server or hostname, for example
192.168.1.20. - Enter v2rayN’s HTTP or mixed proxy port, for example
10809. - If the page asks for a username and password but no proxy authentication is configured in v2rayN, leave both fields empty.
- Save the settings, run the device’s built-in network test, and then verify the connection in an app that supports the system proxy.
Do not enter 127.0.0.1 in the server field. On a TV, 127.0.0.1 points to the TV itself; on a game console, it points to the console itself. Do not enter the router’s gateway address either, unless the proxy service actually runs on the router. In this setup, the proxy program runs on the computer, so you must enter the computer’s address.
DNS handling depends on the device and app. HTTP proxy requests can usually send the target hostname to the proxy for resolution, but the device’s own connectivity checks, time synchronization, and some app requests may still query local DNS directly. If the proxy test passes but an app cannot resolve domains, check the device DNS and v2rayN’s DNS settings separately instead of blaming every issue on the server.
A game console’s “proxy server” setting does not mean all game traffic will use the proxy. Store pages, downloads, and sign-in pages are more likely to follow the HTTP proxy setting, while online games often use additional protocols and UDP. If you need all traffic from the device to be handled, simply entering an HTTP proxy is usually not enough; a network gateway with the appropriate capabilities must handle it centrally. That is beyond ordinary client port sharing.
Temporarily provide a LAN proxy with v2rayNG
When no computer is conveniently available to leave running, v2rayNG on an Android device can provide a local proxy port in certain network environments. v2rayNG uses the Xray core; its settings can enable LAN connections and show the relevant local SOCKS or HTTP ports. The exact names may change between versions, so follow what is currently shown on the settings page.
The setup process is the same as with v2rayN: first confirm that the selected server works in v2rayNG, then enable LAN access, note the Android device’s address on the current Wi-Fi network and its proxy port, and enter those details on the TV or other device.
There is an easy-to-miss distinction here: enabling VPN mode on an Android device does not mean devices connected to its hotspot automatically inherit the VPN path. Hotspot forwarding, the system VPN, and application listening ports are three separate mechanisms. The reliable test is to place both devices on a LAN that allows them to reach each other, then manually enter the proxy address and port provided by v2rayNG on the target device.
Also watch for the system’s background restrictions. The screen turning off, battery saver starting, switching Wi-Fi networks, or the system reclaiming the background process can interrupt sharing without warning. For temporary use, keep the device powered and allow v2rayNG to run continuously in the background. For long-term stable sharing, a desktop device with a fixed network connection, power source, and address is usually easier to manage.
v2flyNG uses the v2fly core and suits Android configurations that require that core family. Its core choice differs from v2rayNG, but LAN sharing follows the same principles: the program must listen on the LAN interface, the firewall or network isolation must not block access, and the target device must support the corresponding proxy type.
Check four layers in order when it does not connect
Layer 1: Is the address still valid?
Home routers usually assign addresses through DHCP. After a computer restarts, reconnects to Wi-Fi, or renews its lease, 192.168.1.20 may change. A target device still using the old address will suddenly fail to connect. Check the computer’s address again and confirm that the subnets match. For long-term use, reserve a DHCP address for the computer in the router.
Layer 2: Can the devices reach each other?
Guest networks, wireless client isolation, and some hotspot modes prevent devices on the same network from reaching one another. Both devices may still access the router and the internet while being unable to connect to each other’s ports. Move both devices to the primary network, disable client isolation on the current Wi-Fi, or use a wired connection on the same router that permits local access.
Layer 3: Is the port actually listening?
Confirm again that “Allow connections from the LAN” was saved, the core is running, and no other program is using the port. If you changed the port, update the firewall rule and target device as well. The listener disappears while the computer sleeps, and the client may not automatically restore the connection after waking.
If another Windows computer is available, use this command to test the target port:
Test-NetConnection 192.168.1.20 -Port 10809If the TCP test fails, the problem is usually in the LAN, listening address, or firewall; it has not reached the subscription and routing rules yet. If the TCP test succeeds but webpages still do not load, check the selected server, protocol settings, DNS, and the v2rayN logs.
Layer 4: Does the proxy type match?
Entering a SOCKS port on a device that supports HTTP only is one of the most common configuration mistakes. Another is using v2rayN’s management interface, API port, or another local service port as the proxy port. Return to the client’s settings page, verify the port name and number, and do not rely on default values from an old guide.
Websites open, but one app does not work
This is usually not a port problem. The app may bypass the system proxy, use UDP, hard-code DNS, or read proxy settings only during its initial sign-in. Fully quit and relaunch the app, then compare its result with the device browser. If the browser works reliably but a particular app always fails, focus on whether that app supports the system HTTP proxy instead of changing v2rayN subscription parameters again.
The computer works, but other devices time out
Check the listening address and firewall first. Successfully accessing 127.0.0.1 on the computer proves only that the loopback port works; it does not prove that the LAN entry point is reachable. After confirming that the port is bound to 0.0.0.0 or a LAN address, test from another device to verify that the sharing path is connected.
Limit the sharing scope and keep the setup stable
A LAN proxy forwards requests for connected devices, so it should be exposed only on a trusted home network. Before leaving home, disable “Allow connections from the LAN,” or make the firewall rule apply only to the Private network profile. Never map the proxy port to the router’s public interface, and do not use a broad inbound rule that permits any source.
If your home has many devices, keep a short sharing checklist: proxy host address, HTTP port, client responsible for running the proxy, and allowed subnet. When you change the v2rayN port or switch networks, update every device from the checklist. This is more reliable than depending on a historical default port.
Traffic routing is still determined by the client providing the proxy. The target device only knows to send requests to the computer; it does not know about VMess, VLESS, transport layers, or subscription groups. v2rayN uses its current routing rules to decide whether a request goes direct, through the proxy, or is blocked. If a LAN device can reach the port but certain domains take an unexpected route, check v2rayN’s routing and DNS settings instead of looking for protocol options on the TV.
After setup, run three checks: once after restarting the client, once after the computer reconnects to the network, and once after rebooting the target device. If an address change causes failure, reserve a DHCP address; if sleep causes failure, adjust the computer’s power settings; if the port rule disappears, review the firewall rule scope. Stabilizing these changing points turns LAN sharing from a one-off test into a repeatable connection.