Hi  @corkscrew22 

Yes, we can use an OC200 to manage SDN devices in a remote site. Below is the guide:

How to Manage Omada Devices at Different Sites Using Omada SDN Controller via Port Forwarding (Controller 5.0 or Above)

  @Vincent-TP Hi yes i have followed the guide you mentioned

Step1 set up port fwd via the oc200 hardware controller on the home nework done ok

For step 2 on the remote network (set up at home and connected to with my laptop) am trying to use method 2 Standalone management page, under controller inform URL it will not accept the url for my no ip ddns server i am using the following format as per the noip instructions

http://username:password@dynupdate.no-ip.com/nic/update?hostname=domain&myip=ip

the ddns host is working i can see it via nslookup

maybe tp-link er605 needs different format ?

 Hi @corkscrew22 

I should mention that we should open ports 29810-29816, two more ports.

Please have another try.

  @Vincent-TP tried that made no difference...

I still think its somthing to do with in the "controller inform url" will not except the noip url in the format below

http://username:password@dynupdate.no-ip.com/nic/update?hostname=domain&myip=ip

it will except xxxx.ddns.net but thats obviousley no use on its own without the log in credentials....

Hi  @corkscrew22 

The inform URL on that page is specially for cloud-based controllers.

For the hardware controller, please input the public IP address.