EAP245 would be disconnected after moving to other site on Omada Controller
Currently I'm deploying Omada Software Controller & having problem in move to other site & manage EAP.
EAP245v3 (US1) --- Gateway A --- Internet --- Gateway B (NAT Forwarding 29810-29814) --- Omada Software Controller
Omada Software Controller could discover EAP245 from Site A with Gateway A by discovery utility tool
=> EAP245 can be adopted by Omada Controller Software Controller successful
EAP245 would be "disconnected" with Controller & couldn't be re-connected automatically after moving to other site on Controller
Please could TP-Link team check this problem and give us your solution soon ?
Looking forward to hearing from you side.