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
Presumably you have tried the potential resolution on the other thread?
"After setting QoS to default, and removing all devices from the high priotity list, the port forwarding has worked as expected for me."
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Bump.. its there going to be an update? These are smart devices.. expensive, I got a 3 pack. No reason why something basic can't be available in an update. That is the whole point of getting expensive feature rich devices. It will be really unfortunate to not have the basic functionality
Update: It works for me. I had to remove the priority devices and things are back to normal.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
They finally released a firmware update that solved this bug. Instructions are here somewhere else on the forum
- Copy Link
- Report Inappropriate Content
I am having the same issue with Home Assistant since moving to Deco M9. It seems like it was resolved for you!
I've updated the Decos and disabled Antivirus. I also don't have any priority devices.
Any help is appreciated.
Thanks in advance.
- Copy Link
- Report Inappropriate Content
It seems that your problem is solved. Could you please more specific which firmware solved the problem.
I have the same problem. But when I go to firmware update, it says mine was already up to date, although the version is only 1.2.12 Build 20191014 Rel. 42025
I don't think that it is the firmware released in 20191014 that solved your problem.
Thanks a lot
- Copy Link
- Report Inappropriate Content
I'm running 1.5.1 build 20210126 now; but if I remember correctly the one before that fixed the issue.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 7382
Replies: 19
Voters 0
No one has voted for it yet.