Explore the guide library · Internet connection setup
Compare local-address and public-name access before assuming a working external service needs more open ports.
If an authorized home service works from another connection but fails through its public name on home Wi-Fi, investigate the local path before changing forwarding rules. NAT loopback, sometimes called hairpin NAT, is one possible difference between the two tests.
Make a three-result table
Test the service through its supported local address while at home. Then test its public name from home. Finally, test the same public name from a separate connection using your own authorized device. Record the exact error and whether the application uses the same protocol and port.
Understand the loopback role
TP-Link explains loopback as handling a local client’s attempt to reach an internal service through the router’s public-side address. Support and behavior vary by model and operating mode. Do not assume every router exposes a switch with that exact name.
Check name resolution
A public name may resolve differently inside and outside the home. Inspect the intended DNS result without publishing the full address. If the name points to an old connection or the wrong service, the problem is not necessarily loopback.
Choose a supported local route
- Use the service’s supported local address when appropriate.
- Consider documented local DNS behavior if the application requires a consistent name.
- Check certificate-name requirements before substituting an address in an HTTPS application.
- Consult the router’s current loopback documentation.
Avoid widening exposure
If remote access already works, adding broad forwarding or enabling DMZ is unlikely to explain the difference between the two local paths. Keep the existing exposure limited to its authorized purpose.
After a supported correction, repeat all three tests and record the result. Also verify behavior after a router restart or public-address change if dynamic DNS is involved. A clear comparison separates local routing and name-resolution issues from genuinely broken external access.
Sources and editorial notes
Sources checked 8 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.