@CS2 

 

inform url is my. controller. com, you need to portforward 29810-29815. to the controller, 29815 is a new port in 5.11.x so you might as well include it as well

 

I use no-ip and it works very well. even after a restart of the router, the remote device adopt quite a short time later. 1 min or so.

I also use the ddns service on the router.

 

you also need to portforward 443 or 8043 (Management port) a bit depending on which controller you are using. this for firmware updates of the remote site device

 

 

Hello,
Thank you for your quick reply and the tip about the additional port that will be required in the future.

It seems you have a similar setup. It seems that the error lies with me or in front of the screen. :-)
Just to be sure: if I enter the following as inform url at site 2:

1. dynamic WAN IP of site 1 (123.123.123.123) -> ER-605 of site 2 is avaible for adoption at the controller and I can adopt it. However, this is not a solution due to the dynamic IP.
2. DDNS address (abc.ddns.net) of site 1 for WAN -> ER-605 of site 2 is not avaible for adoption on the controller. However, the name resolution works on the part of site 2, since site 1 can be pinged under the DDNS address.

 

Since the 1st variant (dynamic IP) works, the port forwarding is set correctly.

Do you see any error in my entries?

  @CS2 

it looks right so there must be something wrong with the ddns setup

 

The ER605 can't be pinged deafult, so if you haven't switched on ping from wan, it shouldn't respond.

you must check that the IP address is correct in relation to the ddns name. ping the ddns name and note the ip address, then go to the router and see which ip address the router has on the wan.

you find it by clicking on the router, you find it on details, wan

If this IP address matches the one you have on the ddns name, it should work.

 

I activated the ping response on the ER-605 to make sure there was a connection possibility.

The IP address is identical between DDNS and WAN IP of site 1: when I use the ping function (System Tools: Diagnostics) with the DDNS address (abc.ddns.net) of the ER-605 at site 2, it resolves the IP address correctly.

 

With the DDNS provider, it is a type A entry for name resolution, which should be correct.

  @CS2 

 

Hmmm, strange,

ok, do you have tryed omada discovery tool on remote site? run discovery tool and enter ddns name, if you have many device you can do a batch config. you ned site username and password if device is adopted before.

if not its username and password you have configured device with. I have som remote site and this have always worked with no issu so strange.

 

 

  @CS2 

 

You can also try portforward management port hardware controller 443 or software contrller 8043 if you not have chaged managementport.

then you should have access to controller from remote site with ddns name. if this work is communication ok.

yep, i tried it now with the discovery utility: it doesnt work neither.

 

I am logged out of the controller with the message: "Note: This Gateway is being managed by Omada Controller 192.168.0.100". This IP address is the laptop on which the discovery tool is running. However, I can log back on to the ER-605 at the remote site.
In the discovery utility I get an "Adopt timeout".

 

at the second attempt with the tool: "Setting succeed". However, the ER-605 of the remote location is not displayed on the controller and I can still log in to the router with the local data. (No, managed by controller or similar appears).

  @CS2 

 

remote router is managed by 192.168.0.100? this will not work if you not have a vpn to site with controller. 

 

try and portforward management port and se if you can access the controller from remote site with ddns name

 

also disable all firewall settings on computer that have controller installed. 

sorry, no: 192.168.0.100 is only the computer with which I am on the router's web interface.

  @CS2 

 

if you go to router wiht your web browser, what do the router say on remote router?

 

this is one of my remote routers