Hi, Right now, our Aredn mesh has 47 nodes and 110 devices. A lot of ham QTH nodes (mostly hAPac Lites with a legacy tunnel) are not currently connected but come and go over time. The first week of November, we have a state-wide simulated emergency test (SET) and, since OLSR is working OK, We delayed the transition to Babel until after this year's SET. We have a lot of tunnels but, also a point-to-point RF mesh (mesh of strings) that spans maybe a dozen institutions, our "medical mesh". The SET will be over in ~ a couple weeks. Then it is time to make the transition. I am looking for advice on how to do this in an orderly manner. I'm sure there are situations that arise, analogous to "cutting off the branch you are sitting on". I'd like to avoid these ;-)
We're running a mixture of older firmware, the most recent and maybe most prevalent is 3.24.10.0 . Maybe we go to 3.25.10.0 for both babel and OLSR compatibility and then go to a pure Babel version??? I suspect we should treat the hAP ac Lites differently because of their memory issues.
Is there a guide on this somewhere I've missed? Any "just make sure you don't do this" situations you can think of?
Thanks for any suggestions! 73,
Lee
kf7yrs
We're running a mixture of older firmware, the most recent and maybe most prevalent is 3.24.10.0 . Maybe we go to 3.25.10.0 for both babel and OLSR compatibility and then go to a pure Babel version??? I suspect we should treat the hAP ac Lites differently because of their memory issues.
Is there a guide on this somewhere I've missed? Any "just make sure you don't do this" situations you can think of?
Thanks for any suggestions! 73,
Lee
kf7yrs
And having the hap AC Lites on Babel-only will relieve some memory pressure on them.
73
Or W6BI