It seems that I am noticing some instability with AirRouter nodes on the latest Nightly version 84 and possibly back to production 3.20.3.1 They increase load factor and then go unavailable on the network but are still seen on the node list. I have not been able to obtain a diagnostic dump as of yet. I believe this usually happens with nodes that do not have RF buddies like has happened way long before.
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Tom, same problem here as well with all versions dating back to 3.18.9.0
Denis
So it's now been 2 days up and running with an RF buddy on this AirRouter AR on Nightly 84 and load figures are still low: .31, .17, .09 | Definite improvement compared to running with no RF buddy or RF disabled. Stable operation so far. I believe we also have a situation where an AirRouter without an RF buddy DTD'd to a Mikrotik HAP (no RF) also runs stable with no issues.
I guess I will sacrifice another AirRouter "buddy" to my problem and see if that solves my 3 year mystery! It always starts out running fine until the next day and then it's on again and off again.
Yes, I've been running all this time since my initial report with an RF buddy on this unit and everything has been stable. I do remember some cases where I have had a non-RF DTD HAP buddy that also seemed to stabilize the situation, but another AirRouter nearby does the trick. Remember to to run them too close to each other on high power settings. Also set your distance parameter to 1km (not 0=auto).
Note in the on-node helpfile, if you have nodes relatively close in proximity, always use a static distance settings. the auto-distance settings is terrible at these short distances. Auto distance works best when distance is in kilometers, and there are not a lot of neighbors coming and going.
Joe AE6XE
Thanks Tom good information!
Denis