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
- When TUN captures the node entry again, the proxy connection can loop back into itself and the interface may show -1 latency.
- Use the core log and read-only route output to confirm the path before changing a route.
- A host route changes the macOS routing table; add one temporarily only when the physical gateway is confirmed and the loop is evidenced.
- Verify both the route and a real HTTPS request through the target node; neither a route lookup nor a latency check is enough alone.
Separate an entry loop from other TUN failures
If explicit proxy traffic works with TUN off but the node connection fails after TUN is enabled on macOS, check whether the Xray log shows the node entry being treated as TUN traffic. A -1 latency result is a clue, not proof of a loop or a failed node.
The defining loop is that the proxy core needs to connect to its server entry, but TUN captures that connection and sends it back to the local proxy port. If the log does not show this path, or the route lookup uses the physical network, stop the route-fix branch and investigate core startup, DNS, node settings, or another network extension instead.
Record the core, entry, and TUN state
Record the macOS and v2rayN versions, the core that is actually running, TUN state, and the node being tested. Confirm that the log belongs to the current client and selected test node, then use one real request through the explicit proxy as a control. Do not use another active node’s exit to prove this node works.
A Mac can have system network extensions, other VPNs, or several utun interfaces. An interface name alone does not identify the component at fault; match the node entry in the core log to the interface and gateway shown by route.
Use read-only route checks to verify the entry path
The route-change examples in this section apply only to an IPv4 node entry. If the active configuration uses an IPv6 address, do not put it into the IPv4 host-route command below. First verify the IPv6 route, physical interface, and gateway separately, then prepare a change and rollback using the platform’s IPv6 route syntax. If that scope is unclear, stay with read-only checks.
A node hostname may resolve to more than one address or change over time. Use the entry address in the client’s current configuration and current resolution; do not turn an old address into a permanent bypass rule. Before sharing terminal output, redact node addresses, the local gateway, and device names.
Read the route to the node entry
shNODE_ENTRY_IP='<NODE_ENTRY_IP>'
route -n get "$NODE_ENTRY_IP"
route -n get default
Add a temporary host route only when the loop is confirmed
Read the physical gateway from the active Wi-Fi or Ethernet network details, and confirm that it belongs to the physical interface rather than TUN. Then add a single-host route for the current node entry so that connection uses the physical network. Do not change the default route, DNS, interface configuration, or firewall.
The command requires administrator privileges and changes the macOS route table. Do not run it if the entry already uses the physical interface or if the correct gateway is unknown. Do not assume the current entry address is permanent; check again after a server address or network change.
Add a temporary host route only after confirming the loop
shNODE_ENTRY_IP='<NODE_ENTRY_IP>'
PHYSICAL_GATEWAY='<PHYSICAL_GATEWAY>'
sudo route -n add -host "$NODE_ENTRY_IP" "$PHYSICAL_GATEWAY"
Keep a rollback path and consider a managed bypass rule
A temporary host route is useful for diagnosis and short-term recovery, but it may not survive Wi-Fi changes, reconnects, or a node-entry change. If the installed v2rayN version provides an entry bypass or exclusion setting, use a client-managed rule only after confirming its target and recording the original setting.
If the route does not help or the route result is unexpected, remove only the host route added for this check. Do not flush the routing table or remove an unknown utun, network extension, or VPN configuration.
Remove only the host route added above
shNODE_ENTRY_IP='<NODE_ENTRY_IP>'
sudo route -n delete -host "$NODE_ENTRY_IP"
Verify the route and real proxy traffic
After adding the route, query the node-entry route again and confirm it uses the physical interface. Fully exit and restart v2rayN, enable TUN, then send a new HTTPS request through the node being diagnosed and confirm in the core log that it reached the intended entry. Record the TUN request and latency result separately.
If the route is correct but the request still fails, the bypass alone did not solve the issue; follow the new core and connection evidence. If real traffic works but latency remains -1, return to the probe branch instead of expanding the route change.
Sources
Frequently Asked Questions
Does -1 latency after enabling TUN mean a node-entry loop?
No. Check whether the core log sends the node entry back into the local proxy, then use a route lookup to identify the actual interface.
Can I add a host route to the node entry right away?
Only when the log and route output both support TUN capture of the entry and the correct physical gateway is known. A host route changes the system routing table.
Is a host route a permanent fix?
Do not assume so. Recheck after a network or entry-address change. A client-managed entry bypass, when supported, may be easier to maintain.
What if pages still fail after adding the route?
Recheck the entry route and core log, then test real HTTPS through the target node. If the entry uses the physical network, investigate the core, DNS, or other network extensions without broadening the route change.