NAT Loopback on R9000 and QNAP´s DDNS

---

nickiman wrote:

According with this article NAT Loopback should work in my R9000 router.

---

It does work in general.

Ignore everything about DDNS - you can run this where ever you want, you can rund DDNS (of course for different services) on the router, multiple NAS, where ever. The name(s) used are not relevant - the IP address resolved is, this is where the connection goes to.

---

nickiman wrote:

But I can´t reach to my DDNS domain of my QNAP NAS from my local network... Is there anyway to enable it?

I´ve disabled Dynamic DNS feature in the router. But, it doesn´t work also even configured and enabled it.

---

For a test, forward 8080/TCP to the QNAP ... or e.g. SSH 22/TCP ... and you might agree on what I wrote above.

However, 443/TCP does not work at all! On might think that active services on the R9000 block the access. However, even if moving the https LAN acess away from 443/TCP, even if re-configuring the ReadyShare https access to a diferent port ... https to a forwarded system like the QNAP don't work. Neither as NAT loopback nor as a real access from abroad.

Either the R9000 does continue using or reserving the port 433/TCP for what ever, or some iptables are blocking 443/TCP - so no https on the default port.

Some more fun? Try the myQNAPcloud Automatic Router Configuration for https 443/TCP ... the R9000 does accept the setting, and does report it back if UPnP queried. In the case of other ports (say 8080/TCP for example), if the port is already occupied by manual port forwarding or by UPnP PMP, there will eb an error reported to the PMP control, and e.g. the QNAP NAS does try higher ports like 8081 or 8082 it will create a port forwarding for 8082 on the WAN to 8080 on the LAN IP. This works - however the NAT loopback does not.

Seen that many times. Reported this many times to Netgear. Answered on the QNAP Community several similar posts the last 15 years or so.

It's 100% a Netgear issue. The issue exists on many more Netgear routers, too.

Netgear consumer routers are ********* because the firmware desing and implementation s**s. And Netgear does gives a s**t about.

Now shout, cry, or whatever. But please don't forget to remove the test port forwards again please 8-)

Christian_R even years after the R9000 (and many other routers) are launched, years after I had repeatedly posted these isues - there is still nothing fixed. It's so disappointing.

Don't know if Voxel has fixed these two issues or not - I insist that Netgear has to fix thier bugware.