Asus Zenwifi BT10

[wrink]

Did you get this firmware update? ZenWiFi_BT10 : 3.0.0.6.102_36808-g0393d96_1036-g1e6e7_BB0B.

I'm not at home right now and traveling, so will have to check when I get back home -- However, I might be a little conservative with firmware updates myself - since I have a currently working stable system - have you updated already, and how do you find it ?

Long term, I hope Merlin/Gnuton adopts the BT10 - as I've come to trust Merlin's supervision and stabilization of Asus' firmware - but that's just a wish depending on many factors such as Asus' release of GPL code to merlin and such. Gnuton is running a poll on Github which hardware to support on Github, so feel free to vote there, if you'd like. Maybe he will start another poll for 2025!

 

[Brookie55]

I'm not at home right now and traveling, so will have to check when I get back home -- However, I might be a little conservative with firmware updates myself - since I have a currently working stable system - have you updated already, and how do you find it ?

Long term, I hope Merlin/Gnuton adopts the BT10 - as I've come to trust Merlin's supervision and stabilization of Asus' firmware - but that's just a wish depending on many factors such as Asus' release of GPL code to merlin and such. Gnuton is running a poll on Github which hardware to support on Github, so feel free to vote there, if you'd like. Maybe he will start another poll for 2025!

So far, so good. I am neophyte as far as networks go so I know next to nothing. Trying to learn.

It's not even on the support page yet. I haven't seen the notes either so we'll see... But seems to be working fine. I have tested all my devices etc.

 

[jzchen]

Just a little tidbit on AiMesh sometimes it takes time to distribute clients to nodes. For example if you have different router models in Mesh and a node is flashed a firmware update, then clients seem/tend to avoid that node for a while, similar to a node going down for whatever reason...

 

[wrink]

Just a little tidbit on AiMesh sometimes it takes time to distribute clients to nodes. For example if you have different router models in Mesh and a node is flashed a firmware update, then clients seem/tend to avoid that node for a while, similar to a node going down for whatever reason...

Yes, thanks for pointing that out. Also, it seems beam-forming-like adjustments seem to improve/adjust signals a bit from the main to the satellite node (I've seen the signal quality to the satellite node improve with time in the main's wireless logs) - so the overall mesh definitely needs a little time to "settle down".

(Also, for my own set up, I've adjusted the RSSI roaming-threshold to be -60 dBm from the default -70 dBm, to result in more aggressive roaming. However, that's only for my specific topology and constitution of the mesh, and one should experiment with their own specific set-up, to find the optimal threshold for themselves - or just leave it alone)