Dear @UdoD,

UdoD wrote

Error scenario (reproducable):

1 Configure R605 as DHCP enabled, Gateway/DNS: IP of FritzBox ==> DHCP works fine

2 Adopt R605 in OC200 Omada ==> Connected, but DHCP stops working

3 "Force Provision" of R605 in Omada ==> DHCP works only for a few seconds during disconnect/connect process.

4 "Forget" of R605 in Omada ==> Obviously R605 resets automatically to 192.168.0.1.

5 Adopt IP-Adress and Gateway/DNS to 192.168.2.x in R605 directly ==> DHCP works fine

6 (same as 2) Adopt R605 in OC200 Omada ==> Connected, but DHCP stops working

The default DHCP Range in OC200 is 192.168.0.X/24, once the R605 is adopted, the settings on OC200 will apply to the R605. 

If you want the R605 to work with DHCP Range 192.168.2.x, after you adopt R605 in OC200, please navigate to Settings -> Wired Networks -> LAN -> Networks, then change the Gateway/Subnet as you want and Update DHCP Range. 

Dear @UdoD,

UdoD wrote

I did a lot of investigation today and want to make public what I experienced.

If you want to adopt a ER605 (TL-R605) to an OC200 and the target network is not 192.168.0.x you can/must do following circumvention:

• Reset ER605 and preconfigure it offline via 192.168.0.1:
  First deactivate DHCP (and click save), then set IP address to target network (and click save).
• If your Omada Controller is not yet on your target IP address: Reset OC200 and preconfigure it offline via 192.168.0.253:
  Set IP address to your target network.
• Now bring both devices online (to your target network).
• If now in <OMADA–Settings–WiredNetworks–LAN> the Subnet is already as wanted then just adopt the ER605. 
• But if the subnet is still 192.168.0.1/24 then be prepared to be quick!
  Click on adopt for the ER605. While it is adopting switch to <Settings–WiredNetworks–LAN> and now you can and must edit the interface and set the IP address to your target network. Nevertheless, don't mind. The adoption will fail and the ER605 gets into unusable status. Now you must again reset the ER605 and preconfigure it again and adopt it again. But now it will get properly connected when you adopt it.
• Additionally and what has been my original issue:
  Looks like DHCP after adoption will only work when you DEACTIVATE it on ER605 before adoption (not kidding).
   

Honestly I still love OMADA SDN.

Thank you for your valued feedback. We appreciate it.

The current Omada SDN Controller doesn't support editing the LAN interface on Omada gateway before the adoption for the time being, which may result in such situation you met, it will be supported in the future to improve the adoption process in different subnets.