Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- In an OpenWrt or KWRT PassWall chain, separate a reachable TCP port from a failed full SOCKS5 request.
- Check whether the client device matches the intended ACL and whether the upstream SOCKS5 port is included in the corresponding TCP forwarding range.
- Change only the smallest range required for the confirmed chain, then retest the full SOCKS5 request in the original app.
- If the application's real traffic uses UDP, validate UDP rules separately; TCP success does not establish that UDP is required.
Separate a TCP probe from a complete SOCKS5 request
If PassWall is configured for a proxy chain on OpenWrt or KWRT, a TCP port probe may reach the SOCKS5 upstream while AdsPower's full SOCKS5 request still fails. These checks measure different stages. A TCP probe only checks whether a connection can be established to one address and port; a SOCKS5 request also needs protocol negotiation, authentication, destination resolution, and forwarding.
If the same upstream proxy completes a request through another client, that narrows the scope but does not identify which PassWall rule is wrong. Record the TCP result, the SOCKS handshake error category, and the destination request separately. Do not treat a successful TCP probe as proof that the proxy chain works.
Confirm the device ACL and the actual upstream SOCKS5 port
Use the PassWall interface to read the active device ACL, proxy-chain mode, TCP forwarding range, and upstream SOCKS5 port. Confirm that the device running AdsPower actually matches the router rule and that the required port is covered by the chain's range. Interface names and rule structure vary by version; do not copy a sample port range from another router.
CLI or interface output may include device addresses, upstream proxy hosts, and ports. Keep only conclusions such as whether a rule matched and whether the required port is covered. Remove real addresses, port combinations, credentials, and configuration content.
Check the TCP connection from the Windows client
The TCP probe in this diagnostic branch runs on the Windows client; it does not assume a particular netcat implementation in an OpenWrt Shell. From the Windows PC behind PassWall, use PowerShell to read TCP connectivity to the same SOCKS5 entry. This checks only for a transport response. Even if it succeeds, it does not prove that PassWall sent the entry connection through the first proxy, and it does not replace a complete SOCKS5 handshake.
Run the comparison from the same Windows PC and network. If TCP succeeds but AdsPower still receives a reset during the full SOCKS5 request, check the PassWall device ACL, TCP forwarding range, and protocol request. Do not open outbound rules for every device because a port probe connects.
Read TCP connectivity from Windows to the SOCKS5 entry
powershell$PROXY_HOST = 'REPLACE_WITH_SOCKS_PROXY_HOST'
$PROXY_PORT = 'REPLACE_WITH_SOCKS_PROXY_PORT'
Test-NetConnection -ComputerName $PROXY_HOST -Port $PROXY_PORT -InformationLevel Detailed
Change the TCP forwarding range only after confirming the match
Consider extending the TCP range in the matching device rule only when the device matches the intended PassWall ACL, the upstream SOCKS5 port is confirmed, the TCP probe succeeds while the full SOCKS5 request fails, and the current range excludes that port. Include only the ports required by the chain. Do not expand the range to every device or the entire port space.
Changing a rule can affect direct connections, routing, or load balancing for other traffic from that device. Record the original ACL and range first, then use the interface for the installed version. Stop if the rule direction or port field is unclear; consult the matching version documentation instead of opening many ports by trial and error.
Retest the full request in AdsPower
After the change, issue a real request with the same device, SOCKS5 configuration, and destination. Confirm that SOCKS5 negotiation and the web request both complete. Then check whether PassWall's current connection view or logs show that connection matching the intended forwarding rule. A reachable TCP port or a saved rule alone does not prove that the chain recovered.
If the request succeeds after the TCP range change, limit the conclusion to that device, rule, and port range. If it still fails, restore the prior range and continue with authentication, DNS, destination connectivity, and policy routing instead of changing several more protocols at once.
UDP requires a separate test
TCP and UDP are different forwarding protocols. If the application's real request uses UDP, confirm the connection and product requirement, then test UDP separately. For a SOCKS5 TCP request, do not change UDP at the same time and call it a required condition.
This diagnostic branch concerns router ACLs, the proxy chain, and forwarding ranges. It differs from a TCP timeout between source servers; a port number alone does not determine whether a service is safe or should be open.
Sources
Frequently Asked Questions
Does a successful TCP probe mean SOCKS5 works?
No. It only checks TCP connectivity. Test the SOCKS5 handshake, authentication, and real destination request separately.
Can I allow the full PassWall forwarding range?
No. Change only the smallest range needed after confirming the device and port rule for the proxy chain.
Does recovery after changing UDP prove UDP is required?
No. TCP and UDP changed together, so there is no separate A/B evidence that UDP was necessary.
Is this the same issue as a source server timing out?
It has a different boundary. A source-host TCP timeout requires checking that host's network path; this issue concerns PassWall device ACLs and forwarding ranges.