@PavelV 

Hey

I have not specifically tried this in the OC200, but I have come across this before with other vendors.   It may have been DLink.. not 100% sure but not important. 

When you created a DHCP range it tied it to a range (/25   128 addresses) for example.  They took the attitude that you could in theory have a 2nd   /25  range in the same network (192.168.0.x) therefore you in theory lock out your device from your own network should you create said 2nd range into which you had placed the controller IP..

I found it a bit strange but sorta made sense, one of the disadvantages of SDN / Autonomous configurations.  One of my colleagues refers to them as "Child Locks", namely designed to help keep you safe but really just create an inconvenience if you are not a child 

@PavelV ,

I also saw that. And I think it makes sense, as you want to manage a whole network (or even a set of) with OC200. The DHCP server is a key component, defining the address ranges of your network(s). When assigning a fixed address via Omada, it is done by the DHCP server. And to avoid confusion, it should be within its own defined address range - not outside of it.

Just my 2 cents ;-)

  Marc