1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

AiMesh evolution - ZenWifi - 3.0.0.386.x firmware branch

Discussion in 'ASUS AX Routers & Adapters' started by Simon W, Mar 20, 2020.

  1. Simon W

    Simon W Regular Contributor

    Joined:
    Jan 7, 2017
    Messages:
    67
    A question to those using ZenWifi devices which I believe runs a 3.0.0.386.x branch of the Asus firmware and in which has a more evolved version of the AiMesh configuration..

    Is there the concept of making certain clients "sticky" to certain nodes?

    This is something I feel is sorely missed in the current (384.x) firmware, especially for geographically fixed clients (eg. IP security cameras) that themselves make poor wi-fi life-choices :)

    While some better clients constantly look to to switch to an optimal node, others just stick to whatever connection they find first.. regardless of whether or not something better comes online later. I often find this is the case when a mesh system is rebooted and with the majority of devices latching onto whichever node comes back online first, some of which then either never or take an age (hours to days) to reconnect to a better option.

    As I understand it the current Roaming Assistant can, if enabled, help this process by forcibly kicking off a client it feels could do better (then leaving it in the hands of the client-side wi-fi gods to do better on reconnection). And there is the option to exclude certain clients from the Roaming Assistant too, which would make sense for fixed-position clients though assuming they get it right in the first place. But what there doesn't seem to be the option for is to stick a given client to a given node - ie. yes I want to roam a client to a given preferred node, assuming it's available, but once it's there I want you to leave it alone (and of course if the node goes down then the client itself will sort out a reconnection to elsewhere)!

    <here's hoping!>
     
    Last edited: Mar 20, 2020
    Grisu likes this.
  2. L&LD

    L&LD Part of the Furniture

    Joined:
    Dec 9, 2013
    Messages:
    13,035
    Routers can't make clients 'sticky'.

    Clients control that aspect of the connection.
     
  3. Simon W

    Simon W Regular Contributor

    Joined:
    Jan 7, 2017
    Messages:
    67
    In part yes, though if you re-read my post, they can (could) certainly help achieve a similar result. The Roaming Assistant, as I understand it, is a blunt instrument: kicks off a client it thinks could be better connected in the hope the client does better when it reconnects. What I'm hoping for is a bit more configurable smarts on the router side: kicking off certain clients in certain conditions, leaving others well alone. Still of course relies the client to do better on its reconnect, but at least forces the decision to be made by specific clients.
     
    Last edited: Mar 20, 2020
  4. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    33,282
    Location:
    Canada
    There's a Roaming Block page somewhere in there - I forgot where. Might be under Network Tools perhaps.
     
  5. AndreiV

    AndreiV Very Senior Member

    Joined:
    Aug 25, 2015
    Messages:
    1,157
    It's the last tab in the Wireless section on the AX92U
     
  6. Grisu

    Grisu Part of the Furniture

    Joined:
    Aug 28, 2014
    Messages:
    3,136
    Ask Asus for feature request, this is exactly why you cant really use blocking right now. Like many other things good idea and bad or very poor implementation ...
     
    Simon W likes this.