Simon W
Regular Contributor
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!>
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:
