TL-R605 / Omada blocks synology.me traffic?
Is there a workaround for port forwarding DDNS traffic from synology.me?
I don't quite understand why a DDNS would need to "be compatible" if the TP-link device isn't running the DDNS host or client. Why wouldn't it simply be trafic coming in to the router to follow the port forwarding rules?
I don't have any DDNS set up on the router or in the controller.
My No-IP DDNS address xxxxxx.servebeer.com works fine.
My Synology DDNS address -- and i'm trying to reach my Synology NAS -- is xxxxx.synology.me, and it takes me to my TP-Link gateway login page and says "Note: This Gateway is being managed by Omada Controller 192.168.0.3"
I don't get it. What gives?