This guide uses v2rayN on a Windows PC to provide an HTTP proxy to a TV box or another PC on the same trusted home network. Find the host’s LAN IPv4 address and actual listening port, configure the client device, then allow access with a firewall rule limited to specific source addresses. If the connection times out, check port reachability first, then verify the proxy protocol and outbound routing.
LAN Sharing Changes the Inbound Listener
Local proxies commonly listen only on the loopback address 127.0.0.1. A browser on the host can connect, but a TV box cannot: on the box, 127.0.0.1 points to the box itself. After enabling “Allow connections from the LAN,” make sure the core listens on an address reachable over your LAN, then connect using the host’s LAN address.
- Host system proxy: Determines whether apps on the host that support the system proxy use it. This setting does not open a port for the TV box. You don’t need to switch the host to “Auto configure system proxy” to share the proxy.
- Client device proxy: Determines where apps on the TV box or another PC send their requests. Enabling sharing does not automatically route traffic from every device, and you don’t need to change the router’s default gateway.
- Host routing rules: Once a request reaches the core, it may still be routed directly, through a proxy, or blocked based on its domain or IP address. Connecting to the shared port does not mean every destination will use the same node.
Find the Host’s IPv4 Address and Shared Port
- Open Command Prompt on the host and run
ipconfig. Find the IPv4 address under the active “Wireless LAN adapter WLAN” or “Ethernet adapter.” Don’t use a virtual network adapter address, the default gateway, or the public address shown by a website. This guide uses192.168.1.20as an example. - In v2rayN, go to “Settings” → “Parameter settings,” then find and enable “Allow connections from the LAN” in the core settings. Menu groups may vary by version, so use the labels in your current interface. If you also see “Use a new port for LAN connections,” check whether it’s enabled. If it is, don’t assume the local port shown in the host’s browser is the shared port.
- Save the changes and apply them as prompted; restart the core if needed. Check the v2rayN logs for port conflicts or core startup errors, then verify the actual listening port. This example uses
10809as an HTTP or mixed-inbound port; the correct value may differ by version.
Check the example port in PowerShell on the host. If LocalAddress is only 127.0.0.1, that IPv4 listener can’t accept connections from the TV box. If it’s 0.0.0.0, the listener accepts connections on all IPv4 interfaces, so it’s especially important to restrict access with the firewall. The result may also show a specific interface address.
Get-NetTCPConnection -State Listen -LocalPort 10809 |
Select-Object LocalAddress, LocalPort, OwningProcess
If there are no listening results, first check the port number and core logs. If you suspect another program is using the port, check OwningProcess against the PID in Task Manager’s “Details” tab. This command only identifies the process listening on TCP; it can’t tell whether the port accepts HTTP or SOCKS.
Configure a TV Box or Another PC
If your TV box’s network settings offer “Proxy” → “Manual,” you’ll usually need to enter an HTTP proxy hostname and port. Some boxes show this option only when editing the current Wi-Fi network, and others don’t offer proxy settings at all. Don’t enter the proxy address as the “Gateway” or “DNS.” If there’s no proxy setting, configure it only in apps that explicitly support proxies.
TV Box: Manual Proxy
- Proxy mode
- Manual
- Proxy hostname
192.168.1.20- Proxy port
10809- Address format
- Enter only the address in the hostname field
Save the network settings, then test with an app that supports the system proxy.
Windows Client PC: System Proxy
- Settings path
- Settings → Network & Internet → Proxy
- Setting
- Manual proxy setup → Use a proxy server
- Address
192.168.1.20- Port
10809
For example, on Windows 11 24H2, open manual proxy settings from the page shown above.
Bottom Line: Choose a Port That Matches the Client’s Protocol
If the settings page supports only HTTP, choose a dedicated inbound or mixed inbound on the host that explicitly accepts HTTP. If the app offers a separate SOCKS5 option, choose a listener that accepts SOCKS5. Don’t guess the protocol from the port number.
Allow Only Specific Devices Through Windows Firewall
Before enabling the listener, make sure you’re on a trusted network you control. Don’t turn off the firewall or add port forwarding on the router just to share the proxy. If the proxy inbound has no authentication, any device that can reach the port may be able to use the host’s outbound connection.
- On the host, run
wf.msc, then go to “Inbound Rules” → “New Rule” → “Custom.” Under “Protocol and Ports,” select TCP and enter the actual shared port as the local port, for example10809. Leave the remote port set to any, since the client device will usually use an ephemeral source port. - Under “Scope,” specify the remote IP addresses to allow, such as the TV box at
192.168.1.42and the client PC at192.168.1.43. Under “Action,” select “Allow the connection.” Under “Profile,” select only “Private” if it matches your trusted home network; don’t select “Public.” - Name the rule, for example “v2rayN Home Proxy TCP 10809.” Check for existing rules that allow the same port or broadly allow inbound connections to the core; a new, narrowly scoped rule won’t restrict the scope of an older rule. If device addresses change often, set up DHCP reservations for them on a router you manage.
Test Port Connectivity Separately from Web Access
First test TCP from the client PC, then make a request to a regular test page using an explicit HTTP proxy. This avoids relying on whether the browser inherits the system proxy. The commands below use an example address and port; replace them with your actual values before running.
Test-NetConnection 192.168.1.20 -Port 10809
curl.exe -I --max-time 10 --proxy http://192.168.1.20:10809 https://example.com/
TcpTestSucceeded : False: Check that the host is online, its current IPv4 address hasn’t changed, the core is listening, and the firewall rule matches the port and source address. Guest Wi-Fi and wireless client isolation can also block connections between devices.TcpTestSucceeded : Truebut the request fails: Check that you haven’t used a SOCKS port as an HTTP port, then review the host’s core logs. If the HTTPS output shows only the response establishing a proxy tunnel, also check the subsequent TLS connection and the destination server’s response. An established tunnel doesn’t mean the page was retrieved.- If the test page loads but an app on the TV box still fails, first check whether the app uses the current network’s proxy settings. Some apps use their own networking stack or rely on UDP traffic that a regular HTTP proxy doesn’t forward. Don’t change firewall rules based on the results from just one app.
Common LAN Proxy Issues
It worked yesterday. Why is it timing out today?
Run ipconfig on the host again to check whether DHCP changed the proxy address. Then check the client device’s network details to make sure its address is still allowed by the firewall. Finally, check whether the host is asleep and whether the v2rayN core is still running.
The TV box and PC are on the same router. Why can’t they connect?
Check whether the TV box is on a guest network or whether wireless client isolation is enabled. Connect the box to a trusted home network that allows devices to communicate, then test again. Don’t disable guest network isolation just to connect one TV box.
Does the TV box need to import the subscription again?
No subscription import is needed if you’re using only the system HTTP proxy. Enter the host address and port on the TV box; manage nodes and routing on the host. If changing nodes affects access to only some addresses, first check whether those addresses match a direct-connection rule.