NAT Loopback in subnetwork
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.NAT Loopback in subnetwork
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I have a TPLink VDSL Modem (TD-W9960 v1 1.2.0 0.8.0 v009d.0 Build 201016 Rel.78709n) and TPLink Access Point (Archer c80 v1 1.5.7 Build 210308 Rel.60033n(4555)) on my network.
A LAN cable (192.168.1.2) reaches the AP working in router mode through its WAN port. They both have Wireless enabled, but I treat the AP as my secure home network.
Modem directs the traffic on all ports to AP with NAT-dmz forwarding. It also uses tplink ddns service to bind subdomain.tplinkdns.com to my public IP.
The AP has some NAT port forwarding settings for various services including http on port 80.
When I connect to the modem's wifi, I can access all ports via the ddns domain. (NAT loopback works even I am on the local network)
But when I connect to the AP's wifi, I cannot access anything on my local network neither using the subdomain nor my public IP.
NAT boost is not activated on neither devices as I read that it disables the NAT loopback.
Can you please help me to figure out how can I enable access to my local network servers via the domain.
Best
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Good catch for the subnet mask setting /32 instead of /24. Try if the default gw 0.0.0.0 will work for the same static route.
If this doesn't work try the second part of my suggestion - using ethernet cable to the W9960 LAN port (from my previos post).
If W9960 still unreachable then follow Kevin's advise.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 23
Replies: 0
Voters 0
No one has voted for it yet.