@r3naissance i noticed the same thing, you can use 10.10.10.1/24 it should give the same result. but there is definitely a bug in the 5.7 controller

@Snakesrules It's probably a bug with the v5 version, but you can play around a bit and see what you find out :-)

@Snakesrules Yes, it looks like the port is open, so that's not the problem. it doesn't seem like the controller supports EAP225 v5, only v3 is in the supported device list, but strange it worked...

@Snakesrules check if TCP port 29814 is blocked on your ubuntu server. try to telnet to the server from a windows pc from command line type. telnet your.ip 29814

@VitaliyT you can log into the app without the controller being in the cloud, add it as a local controller in the app

@KimcheeGUN according to TP-Link, this appears to be completely normal.