Network Management

last person joined: 8 hours ago 

Keep an informative eye on your network with HPE Aruba Networking network management solutions
Expand all | Collapse all

Bind client to specific BSSID

This thread has been viewed 1 times
  • 1.  Bind client to specific BSSID

    Posted Feb 13, 2015 09:58 AM

    Hello, 

     

    we have some users with samsung android who are running a specific application (connects to a cloud server) that does not support roaming.

    If the client roams between APs connection is dropped.

    However, this clients are only used to a specific room.

     

    Is it possible to bind these clients to a specific AP nearby and prevent the controller from sending De-auth (client match)?

     

    thanks



  • 2.  RE: Bind client to specific BSSID

    EMPLOYEE
    Posted Feb 13, 2015 10:07 AM
    No this is not possible. There are utilities/apps out there that can be
    installed on the client that can lock it to a certain BSSID.


  • 3.  RE: Bind client to specific BSSID

    Posted Feb 13, 2015 11:11 AM

    However, this wouldn't prevent the controller from deauthenticating the client occasionally... 

    Maybe, it should be considered as a feature or something.



  • 4.  RE: Bind client to specific BSSID

    EMPLOYEE
    Posted Feb 13, 2015 11:52 AM

    Regrettably, this is another example of a poorly written application.  You should contact the developers and complain.



  • 5.  RE: Bind client to specific BSSID
    Best Answer

    EMPLOYEE
    Posted Feb 13, 2015 02:49 PM

    Gem,

     

    There is no configuration that would allow the controller to only allow a client to connect to a specific SSID.

     

    If you want the controller to NOT make any client moves using clientmatch, you can add the client to the clientmatch unsupported list:  http://community.arubanetworks.com/t5/Controller-Based-WLANs/HOW-TO-DISABLE-CLIENT-MATCH-FOR-A-SPECIFIC-CLIENT/ta-p/179938

     

     



  • 6.  RE: Bind client to specific BSSID

    Posted Feb 21, 2015 04:36 AM

    Thanks all.

    Combination of all three answers is the way to go.

     

    Temporary workaround:

    Disable ARM on the controller so it doesn't de-auth clients.

    Install an app on the device to bind to specific AP.

     

    Finally have the developers fix their poorly written app, as they have agreed that they have the problem elsewhere and they need to address it.