This guide is for anyone already using v2rayN on a PC who wants to share its proxy with an Android phone or another computer on the same home network. First check the proxy’s listening address and port, then enter the host PC’s local IP on the other device. Finally, use a port test and the logs to distinguish firewall issues from network isolation or node problems. The instructions focus on Windows as the host, using port 10808 as an example. Use the values shown in your client.
How LAN proxy sharing works
“Allow connections from the LAN” exposes a local proxy endpoint managed by the v2rayN core; it does not copy your node configuration to another device. Your phone sends requests to the host PC, which then routes them directly or through a proxy according to its current rules. The host must stay powered on, with the core running and its network connection active. Other devices lose access to the proxy when the PC goes to sleep.
Keep “system proxy” and “LAN listening” separate. A system proxy setting tells compatible apps on the PC where to connect. LAN listening lets other devices reach the PC’s proxy port. Selecting “Set system proxy” from the tray menu alone will not connect your phone. Conversely, when sharing with other devices, the host PC does not need its own system proxy setting enabled to accept their requests.
- Check the host first: Select a working node on the PC and confirm that websites load before enabling sharing.
- Use a trusted network: Connect the PC and phone to your home router’s regular network. Don’t expose the proxy on public Wi-Fi.
- Rule out other proxies: Temporarily disable other proxy or VPN connections on the receiving device so they don’t reroute traffic.
Step 1: Enable LAN access and check the port
Open the v2rayN main window and go to “Settings” → “Settings”. In the basic settings page, look for an option such as “Allow connections from the LAN” under “Core: Basic settings” and turn it on. Group names and punctuation vary between versions, so follow the meaning of the setting. Save your changes and restart the core if prompted. If there’s no restart prompt, quit and relaunch v2rayN, then make sure the selected node still works.
- Note the “Local mixed listening port” or the corresponding local listening port. This guide uses
10808as an example; you don’t need to change your existing port to this value. - Check which protocols the port accepts. A mixed endpoint usually accepts both HTTP and SOCKS. If the interface lists separate HTTP and SOCKS ports, enter the HTTP port in Android’s Wi-Fi proxy settings.
- Don’t enter the node server’s port on your phone. The remote port used by a node is different from the local proxy port that LAN devices connect to.
- After enabling sharing, check that the port is actually listening. If the setting is checked but the core hasn’t reloaded, the port may still be bound only to the loopback address.
Run the command below in Windows PowerShell to check the example port. Replace the number if you use a different port. If there’s no output, check the client logs for startup errors or a port conflict before changing the firewall.
Get-NetTCPConnection -State Listen -LocalPort 10808 |
Select-Object LocalAddress, LocalPort, OwningProcessStep 2: Find your PC’s local IPv4 address
On the host PC, open a terminal and run ipconfig. Find the IPv4 address under the active “Wireless LAN adapter WLAN” or “Ethernet adapter”. Don’t use a disconnected network adapter, virtual adapter, loopback address, or node server address. A PC connected to the router by Ethernet can still communicate with a phone on the same router’s Wi-Fi, as long as no network isolation rules block them.
ipconfig
# Example for illustration only; this is not actual output from your PC:
# IPv4 address: 192.168.1.20
# Subnet mask: 255.255.255.0
# Default gateway: 192.168.1.1Suppose the PC’s address is 192.168.1.20 and the phone’s is 192.168.1.35, with a subnet mask of 255.255.255.0 on both. They’re usually on the same IPv4 subnet. These addresses are examples to show where to enter the values; don’t copy them. The “Gateway” shown in your phone’s network details is usually the router, not the host PC.
Host PC example
- Local IP address
- 192.168.1.20
- Proxy port
- 10808; use the value configured in your client
- Listening scope
- Reachable from trusted devices on the LAN
- Requirements
- PC awake and core running
Get the IP from the active network adapter and the port from the client’s local listening settings.
Receiving device example
- Proxy type
- Manual HTTP proxy
- Host name
- 192.168.1.20
- Port
- 10808
- Network requirement
- Can reach the host PC’s local IP address
Enter only the IP address in the host name field; don’t add a protocol prefix or port.
If the PC’s IP changes every time it restarts, reserve an address for it in your router’s “DHCP reservation” or “static lease” settings. Manually assigning an arbitrary static IP on the PC can cause an address conflict. After reserving an address, check which IP the PC actually receives.
Step 3: Configure the proxy on a phone or another PC
Android: Change the proxy for the current Wi-Fi network
On Android, go to “Settings” → “Network & internet” → “Internet”, open the details for your current Wi-Fi network, and use the edit option to expand “Advanced options”. Set “Proxy” to “Manual”. On some devices, go to “WLAN” → your current network → “Modify network” instead. The labels vary, but you should end up with fields for the proxy host name and port.
- Enter the host PC’s actual local IP address under “Proxy hostname”, for example
192.168.1.20. - Under “Proxy port”, enter the HTTP or mixed listening port, such as
10808. Don’t enter a subscription URL or node port. - Leave “Bypass proxy for” at its default for the initial test. Once the connection works, add local network destinations if needed.
- Save the settings, then use a browser that respects the system proxy to visit
https://example.com. Check the host PC’s logs for the corresponding request.
Windows and macOS: Set a system-wide manual proxy
- Windows 11: Go to “Settings” → “Network & internet” → “Proxy” → “Manual proxy setup” → “Set up”. Turn on “Use a proxy server”, enter the host PC’s address and its HTTP or mixed port, then save.
- macOS: Go to “System Settings” → “Network”, select your current network service, then choose “Details” → “Proxies”. For an HTTP endpoint, enable “Web Proxy (HTTP)” and “Secure Web Proxy (HTTPS)” as needed, and enter the same host address and port for both. The HTTPS option selects a proxy for HTTPS destinations; it does not require TLS on the proxy endpoint itself.
- Linux: Settings vary by desktop environment. In GNOME, go to “Settings” → “Network” → “Network Proxy”, select “Manual”, and enter the corresponding addresses and ports for HTTP and HTTPS. Check separately whether command-line apps use these settings.
Step 4: Add a narrowly scoped inbound firewall rule
If the proxy works on the host PC but connections from other devices time out, check the host’s firewall. Don’t leave the entire firewall disabled for testing, and don’t set up port forwarding on your router. LAN sharing only needs trusted local devices to reach the listening port; there’s no need to expose the proxy to the internet.
- Search for and open “Windows Defender Firewall with Advanced Security” from the Windows Start menu, then go to “Inbound Rules” → “New Rule”.
- Select “Port” → “TCP” → “Specific local ports” and enter the actual listening port, such as
10808. Choose “Allow the connection”. - Select only “Private” for the network profiles. Give the rule a recognizable name, such as “v2rayN home LAN proxy TCP 10808”. Check the network profile in your system’s network properties; don’t casually change a public network to private.
- After creating the rule, open its “Properties” → “Scope” and limit “Remote IP address” to the devices you specify, or enter your actual trusted subnet, such as
192.168.1.0/24. This subnet is an example only. - Test again. If connections are still blocked, check for an explicit block rule or security software that manages inbound traffic separately.
This guide tests a TCP endpoint for an HTTP proxy; there’s no need to open a UDP port with the same number. A port-based rule may also allow other programs that later use that port, so restrict remote addresses. Disable or remove the rule when sharing is no longer needed. If you create a program-based rule, make sure it allows the process that actually listens for connections, not just the v2rayN interface.
In short: Limit access before keeping proxy sharing enabled
Allow only the devices you need on your home network to reach the actual TCP listening port. Don’t forward the port on your router. Once the port test succeeds, move on to browser and routing checks. Changing several things at once makes it harder to find the cause of a problem.
Test in layers: port reachability, proxy response, destination access
When a connection fails, separate node issues from LAN issues first. Run these tests on another computer receiving the proxy, not just on the host PC. Success on the host only confirms that some parts are working; it doesn’t prove that Wi-Fi or the firewall allows other devices to connect.
# Test the TCP port in PowerShell on another Windows PC
Test-NetConnection -ComputerName 192.168.1.20 -Port 10808
# Then explicitly use the HTTP proxy to test access to an HTTPS destination
curl.exe --proxy http://192.168.1.20:10808 --connect-timeout 5 --max-time 20 -I https://example.comIn a macOS or Linux terminal, use curl instead of curl.exe for the second command. Explicitly specifying the proxy avoids the uncertainty of whether an app reads the system proxy settings. --connect-timeout 5 and --max-time 20 set test time limits; they don’t indicate how long a normal connection should take.
| Result | Check first | What to do next |
|---|---|---|
| TCP test fails or times out | Address, listener, firewall, or network isolation | Check the active adapter’s address and the actual listening scope, then review inbound rules |
| Connection refused immediately | No process listening on the port, or an explicit reject rule | Check that the core is running, verify the port number, and inspect the local listening output |
| TCP succeeds, but the proxy request fails | Endpoint protocol, authentication, or core logs | Make sure you entered an HTTP or mixed port, then check the logs for errors at the time of the request |
| Command succeeds, but an app fails | Whether the app uses the system proxy | Check the app’s own network settings instead of widening the firewall rule |
| Some sites work, others fail | Routing, DNS, the node, or the destination site | Compare the destination and outbound result in the client logs, then retest the same destination |
Even if a browser reaches a destination, that doesn’t prove traffic went through a remote node: v2rayN routing rules may send that destination directly. To confirm that the shared endpoint received the request, check the available logs. To verify the outbound route, inspect the matching routing rule and connection record. Don’t treat one successfully opened page as proof that every app and protocol is working.
Common LAN proxy sharing issues
Why does the connection time out when my phone and PC are on the same Wi-Fi?
Check whether the phone is on a guest network and whether the router has “AP isolation”, “client isolation”, or guest access restrictions enabled. Devices on Wi-Fi networks with the same name may still be on different subnets. Compare the IP addresses, subnet masks, and gateways on both devices, then test the TCP port from another PC. A successful or failed ping alone doesn’t tell you whether the proxy port is reachable.
Why can’t my phone connect when I enter 127.0.0.1 as the proxy host?
127.0.0.1 always points to the device you’re using. Entering it on your phone makes the phone try to connect to itself. Use the local IP of the host PC’s active network adapter instead, such as 192.168.1.20 from this example, and check the port again.
Do I need to reconfigure my phone when I change nodes on the PC?
Usually not. Your phone connects to the same local proxy endpoint; the host PC handles node selection and routing. Update the receiving device only if the host PC’s address, listening port, endpoint protocol, or authentication requirements change. Existing connections may drop while switching, so reopen a page to test.
Why do browsers work but games and other apps don’t?
First check whether the app supports the system HTTP proxy. It may use its own networking implementation or rely on UDP traffic that this endpoint doesn’t route. Don’t try opening more firewall ports at random. If you need to run a proxy independently on an Android device, choose v2rayNG or v2flyNG based on your core requirements and follow the relevant setup guide.
Why can’t my phone access the internet after I turn off sharing?
Open the settings for the current Wi-Fi network, change “Proxy” from “Manual” to “None”, and save. Turn off the corresponding manual proxy on other computers as well. Apps that use the proxy will keep trying to connect while the receiving device points to a stopped endpoint. Quitting v2rayN does not automatically clear proxy settings on other devices.
After sharing: final checks
The LAN proxy endpoint uses the host PC’s node, bandwidth, and routing rules. Unless you configure authentication, don’t assume that only devices you set up manually can connect; other reachable devices on the network may also try. Even on a home network, limit access to the devices that actually need it.
- For occasional use: First remove the manual proxy from receiving devices, then turn off “Allow connections from the LAN” and reload the core as prompted.
- Remove the rule: Disable the inbound rule created for this sharing session. Don’t leave unused ports open.
- For regular use: Keep a stable local IP and a narrowly scoped firewall rule. Note the actual port and prevent intermittent disconnects by keeping the PC awake.
- When changing networks: Turn off sharing before taking the PC away from your home network. Once it’s back on a trusted network, check the IP address, network profile, and access scope again.