Business Community > WiFi > Omada Controller - Bind to AP logic.
< WiFi

Omada Controller - Bind to AP logic.

Omada Controller - Bind to AP logic.

Omada Controller - Bind to AP logic.
Omada Controller - Bind to AP logic.
a week ago - last edited a week ago
Tags: #Network Connectivity #Mesh #Bind
Model: EAP610  
Hardware Version: V3
Firmware Version: 1.5.0 Build 20240830 Rel. 63168

Self-hosted Omada Software Controller: v 5.15.20.18
EAP610 v3 Firmware: 1.5.0 Build 20240830 Rel. 63168

 

The "Bind to AP" indeed works as intended. However, once the EAP ap device is "forget" from the Omada controller, all the clients bind to the removed ap cannot connect to other wireless APs.

 

List of clients in the Omada Conroller or the mobile app DO NOT show disconnected devices. Therefore there is no way to remove "Bind to AP" for the forgotten device. This leads the "STATUS" column redundant as it will ONLY shows "Connected", and I know any clients that are in the list are "Connected".

 

From Insights -> Known Clients (this shows disconnected clients) -> <binded device> -> Config -> There is no setting to remove the "Bind to AP". This is related to "forgotten device". Otherwise "Bind to AP" is available for EAP that are online.

 

Currently, the only solution is to re-adopt the forgotten EAP device.

 

Is there another solution to this?

  0      
 
  0      
 
#1
Options
5 Reply
Re:Omada Controller - Bind to AP logic.
a week ago - last edited a week ago

  @Joolsc 

 

When a client is configured with **Lock to AP**, it cannot connect to other APs on the same network unless this setting is disabled.

This is the current working mechanism of **Lock to AP**, so the behavior you described is expected.

 

If you frequently need to forget the locked AP, we recommend disabling this setting.

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#2
Options
Re:Omada Controller - Bind to AP logic.
a week ago

  @Vincent-TP 

 

Thanks for your response,

 

Can you explain how or where to "disable" the settings if the AP has died or forget (removed) from the network? I cannot find that option.

 

The feature "Bind to AP" should only bind if the AP is online. When the AP is offline, the clients that are bind to that ap should be able to connect to nearby AP until the AP they were bind to is online again.

 

Currently, all the clients that are bind to the (dead / removed) ap cannot connect to the WiFi network.

 

To summarize, how do you "unbind to ap", "after" (not before) the AP is dead or removed?

  0  
  0  
#3
Options
Re:Omada Controller - Bind to AP logic.
Monday

Hi  @Joolsc 

 

I understand your question. And actually, you already found out the answer in your first post.

 

 

 how do you "unbind to ap", "after" (not before) the AP is dead or removed?

>>the only solution is to re-adopt the forgotten EAP device.

 

 

BTW, did you try forget the network on the client side? Will this work?

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#4
Options
Re:Omada Controller - Bind to AP logic.
Monday

  @Vincent-TP 

 

My scenarios are simple R --> AP1 )))))) AP2 --> PC1 (Bind to AP2)

 

1) Turned off AP2 (turn off the power)

 

PC1 is shown in "Clients" and able to access the config to disable "Bind to AP" - Good.

PC1 will not connect to nearby AP - Questionable.

 

This means, I need to disable "Bind to AP" to connect to nearby AP.

 

2) AP2 is forgotten

 

PC1 is not listed in the "Clients"

PC1 is shown in -> Insights -> Known Clients

    - "Cannot access "Bind to AP" setting

    - Disconnect / Reconnect from client side (PC1) will not connect to nearby AP. (due to bind)

Delete PC1 from Insights -> Known Clients

    - ** Still cannot connect to nearby AP **

 

After 40mins

 

Adopted AP2 back to controller and PC1 can connect again.

 

Issues encountered:

 

AP2 was resetted using the pin, and when adopting, controller will ask for username and password for this device. This lead to "Adopted Failed" I guess.

 

AP2 adopted via ethernet fine, and was able to mesh wirelessly after a few minutes.

 

--------------------------------------------------------

 

My issue is with the logic, when a device is bind to AP, and when the AP is down, it should connect to nearby AP until it is online again. This mitigate devices from being disconnected for too long (for example 40mins).

 

I may understand your point too, if AP2 has 250 clients binded clients, and AP2 disconnects, nearby APs can partially connect those AP2 clients. But being able to connect to nearby AP until AP2 is online or "port binded clients" to another AP is still better than leaving them disconnected.

 

At the moment, there is no "easy" way to recover binded client "after" AP is forgotten.

 

The network administrator must understand that when the AP is forgotten, all the "Bind to AP" clients for that AP should be disabled / cleared from the settings. It is easier to bind than unbind (near impossible without factory reset the controller perhaps or lucky to re-adopt).

 

The focus here is not the AP, but how quickly to get those clients connected again. (hint 99.999999% uptime) ;D

 

  0  
  0  
#5
Options
Re:Omada Controller - Bind to AP logic.
Tuesday

Hi  @Joolsc 

 

I totally understand and agree with you. However, there is no other quick solution for your request.

 

The current Lock to AP mechanism operates as follows: All other APs adopted in the same site will reject connections from the client's MAC address, and **only the blocked AP** can provide connectivity—hence the awkward situation you're encountering.  

This is why I recommend **avoiding the "Lock to AP" setting** in such cases.  

 

Wish you a happy life and smooth network usage!  >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#6
Options

Information

Helpful: 0

Views: 79

Replies: 5

Tags

Network Connectivity Mesh
Bind
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.