Business CommunityWirelessOmada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)
Wireless

Omada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)

Omada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)

Omada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)
Omada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)
3 weeks ago - last edited Tuesday
Model: EAP725-Wall   EAP655-Wall  
Hardware Version:
Firmware Version:

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.

0
0
#1
1 Accepted Solution
Re:Omada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)-Solution
2 weeks ago - last edited Tuesday

 

Hi,@mgyuri 

Thank you for posting on our business forum.

 

Generally speaking, changing a device's fallback IP should theoretically not affect the IP address assigned to the EAP via DHCP, nor will it impact the communication between the EAP and the controller. The fallback IP only takes effect when no DHCP server is available on the network.

To better assist you with troubleshooting, we would like to kindly confirm the following information with you:

  • Was the EAP operating on a DHCP-enabled network during your configuration process?
  • Could you please inform us of the current firmware version of your EAP, and confirm whether you have already attempted to upgrade the EAP to the latest official firmware?
  • You provided two EAP models in your post; do both devices encounter the same issue?

Thank you very much for your cooperation.

 

Recommended Solution
0
0
#2
1 Reply
Re:Omada v6 — AP fails to reconnect after Fallback IP config push (ap_-6)-Solution
2 weeks ago - last edited Tuesday

 

Hi,@mgyuri 

Thank you for posting on our business forum.

 

Generally speaking, changing a device's fallback IP should theoretically not affect the IP address assigned to the EAP via DHCP, nor will it impact the communication between the EAP and the controller. The fallback IP only takes effect when no DHCP server is available on the network.

To better assist you with troubleshooting, we would like to kindly confirm the following information with you:

  • Was the EAP operating on a DHCP-enabled network during your configuration process?
  • Could you please inform us of the current firmware version of your EAP, and confirm whether you have already attempted to upgrade the EAP to the latest official firmware?
  • You provided two EAP models in your post; do both devices encounter the same issue?

Thank you very much for your cooperation.

 

Recommended Solution
0
0
#2

Information

Helpful: 0

Views: 137

Replies: 1

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.