Hi  @Vincent-TP 
 

Contrary to your statement, Loopback Detection (LBD) was definitely available on the EAP series, at least in firmware version 1.5.0 Build 20250208 for EAP610 v3. I had it enabled on all my access points via Omada Controller.

After upgrading to version 1.6.0 Build 20250507 Rel. 66340, the Loopback Detection option disappeared from:

Site View > Devices > Properties (AP) > Config > Services

To verify this, I downgraded one of my APs back to firmware 1.5.0, and the LBD setting reappeared, exactly as expected. I'm attaching a screenshot to demonstrate this.

In addition, I am also attaching screenshot logs from earlier firmware versions where Loopback Detection triggered and blocked the ETH(PoE) port, clearly proving that the feature was functional and actively monitoring loops on the AP side, not just the switch.

Could you please clarify:

• Was this feature intentionally removed in the latest firmware?

• If not, is LBD still active in the background but now hidden from the interface?

• If still active, how can we disable it (via SSH, CLI, or config override)?

Please forward this to your firmware/dev team if needed.
This is a serious configuration-level change that affects enterprise deployments with hundreds of EAPs like ours.

Thank you.

  @Vincent-TP Hi

Unfortunately, I’m having trouble uploading the log screenshots. Although I select and attach them before publishing the post, they disappear after I click “Post.”

I wanted to include the logs that show the “port ETH(PoE) was blocked due to loopback detected” messages from earlier firmware versions, but due to this issue I couldn’t attach them.

Please let me know if there’s an alternative way to share these files (email, support portal, etc.).

@Vincent-TP Hi;

I tried uploading the image using the method you suggested.

I uploaded this screenshot from the current 1.5.0 firmware, where the Loopback Detection setting is clearly visible and manageable.
Previously, when I was on version 1.6.0, LBD logs were still appearing, but as an end user, I had no control over the feature — the setting was completely missing from the interface. 
This caused confusion because the feature was active, but there was no way to configure or disable it.

  @Vincent-TP 
 

Thank you for your response and clarification.
I would like to share some additional details based on my observations and experience:

1. Loopback logs were generated even when the switch had no loop detection enabled.
In my network, none of the switch ports had Loopback Detection or STP enabled, yet the EAP610 was consistently generating loopback detection logs. I had intentionally left the LBD setting enabled on the EAP to investigate the root cause of these logs, even though no actual loop existed. So it's not accurate to say the switch alone detected the loop.

2. After upgrading to firmware 1.6.0, LBD was not automatically disabled.
If LBD was previously enabled on the EAP610, the upgrade to 1.6.0 does not automatically disable the feature in the background. This could lead to confusion for administrators who can no longer see or manage the option in the UI but still get related logs.

3. I understand that a loop can't occur on a single-ETH-port device.
I'm fully aware of this. However, I deliberately kept LBD enabled to monitor the behavior for troubleshooting purposes. It helped track potential anomalies or false positives within the network.

4. This kind of change should be clearly noted in the release notes.
Removing a visible feature from the UI, especially one that might still be working silently in the background, should be documented in the firmware release notes. Otherwise, it causes unnecessary time loss for administrators trying to understand what changed.

I appreciate your help and hope this feedback can be forwarded to your development or documentation teams. These clarifications would really help in large-scale deployments where every detail matters.

 

Additional Note:
I've seen that loop detection and related false-positive issues have been widely discussed in the community forums.
As someone managing a large-scale enterprise network, I believe there is a need for a more robust loop detection mechanism that can minimize false positives and provide clearer diagnostics.

I'm sharing all this feedback with the intention of helping you improve the system further.