Environment:

• Omada Software Controller v6
• EAP655-Wall, EAP725-Wall (and likely other EAP models)
• AP in controller mode, DHCP active

Steps to reproduce:

1. AP → Config → IP Settings
2. DHCP mode: leave unchanged (already enabled)
3. Enable Fallback IP → enter IP in a different subnet than the AP's current active IP (e.g. current: 192.168.5.x, fallback: 172.16.10.x)
4. Save → confirm security warning
5. AP goes CONFIGURING → DISCONNECTED and stays disconnected
6. Configuration Result: IPv4 Edit — Device response timed out (ErrorCode: ap_-6)

Expected behavior: AP applies the config, reboots if necessary, and reconnects to the controller automatically.

Actual behavior: AP does not reconnect after the config-triggered reboot and remains disconnected indefinitely.

Key observation: A manual power cycle (no config changes) immediately brings the AP back online with the pushed configuration intact and working. This confirms the configuration itself is valid — the AP simply fails to complete its reconnection after a controller-triggered reboot.