Deco M9 plus V2 does not support NAT Loopback / Hairpinning
Deco M9 plus V2 does not support NAT Loopback / Hairpinning
Hi.
Just bought a Deco M9 (v2) set and set up port forwarding. Unfortunatly it's not working as it should. It works only for external (WAN) traffic and not internally (from home).
What I'm doing redirecting a public address to a local one. From the internet to local it works (eg phone connected via 4G), but from the LAN side it doens't (phone on WIFI). As the NAT is used for home automation server this is a very serious limitation. I did not buy router to use 4G iso wifi.
Any tips on how ot enable/fix this? NAT loopback / hairpinning is very common and for me it seems strange that such a expensive device does not support it....
Regards,
R.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
it does not work on this router. It did on two other brands but not on this one. I installed my previous router and it works again!
im very disappointed... the m9 v2 was expensive but it lacks many features.
- Copy Link
- Report Inappropriate Content
Hello, the NAT loopback is enabled by default.
How did you access it from locally with the WAN IP address? Please show us a screenshot of it.
Besides, you can open a port for a local server and verify whether you can access it with LAN IP + port number and WAN IP + port number locally.
Good day.
- Copy Link
- Report Inappropriate Content
Thanks for the quick reply. I'm running a "Home Assistant" server that has a https web interface running on port 8123.
Within the DECO app I added Port Forwarding:
Internal IP: 192.168.178.192
External port: 443
Internal port: 8123
I tried the following testcases:
- WAN (connected from outside world): https://mydummyadress.duckdns.org -> server is responding
- LAN (Connected to DECO M9 WIFI): https://192.168.178.192:8123 -> server is responding
- LAN (Connected to DECO M9 WIFI): https://mydummyadress.duckdns.org -> server is not accesable
Note 1: I have been running the exact same setup with my two previous routers and this always worked.
Note 2: I also tried disabling the DECO virus protection but that was not the problem.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Bump - still no solution....
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello, sorry to respond late.
Have you ever tried to change the DNS on your computer? Like 8.8.8.8 or 8.8.4.4?
Besides, you can change the DNS of the Deco also.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thanks for your reply. I double-checked the information you provided before, you use the domain name to access the server on the LAN network, actually, DDNS just binds the WAN IP and your domain together. We cannot access a website by using the WAN IP or domain if no port forwarding rules are set up for certain servers.
That is to say, you need access the https server via the domain name with the port number.
So it is not a bug; to verify whether DDNS works well, we use 'nslookup' to resolve the domain to see if it leads to the public WAN IP address of Deco. If the domain name can be resolved to an IP address, then DDNS is successfully bound to the IP address.
Good day.
- Copy Link
- Report Inappropriate Content
it does not work on this router. It did on two other brands but not on this one. I installed my previous router and it works again!
im very disappointed... the m9 v2 was expensive but it lacks many features.
- Copy Link
- Report Inappropriate Content
THIS IS UNBELIEVABLE! I just found out you know about this issue!
https://community.tp-link.com/en/home/forum/topic/151141?page=2
This descibes my problem!!!! WHY would you let me spend time on it? It has to be fixed in the new firmware for the M9 V2.
This TP-LINK is a joke and the worst product I have encoutered in a very long time!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 7380
Replies: 19
Voters 0
No one has voted for it yet.