You are here

Questions related to Babel implementation

2 posts / 0 new
Last post
N4SV
Questions related to Babel implementation
I'm just getting around to upgrading the firmware in some legacy hardware and I saw a warning that older hardware with insufficient memory will not be compatible with the Babel routing protocol.  Is it possible to produce a document, referencing the current approved devices list, that would indicate just which of the currently approved devices will not be supported...or is it just a simple matter of device memory, where more is better?  Are there other hardware/firmware considerations other than just memory?  Possibly a particular brand of hardware that might be a better choice to work with Babel?

If I read the Babel announcement correctly, eventually these older devices will simply stop functioning in the future, likely a year or year(s) from now.  I'd just like to be sure I am getting equipment today that, as far as we know now, will be Babel-compatible going forward.  Thanks.
w6bi
w6bi's picture
Babel support
Bill, the devices that won't support Babel going forward are the devices on AREDN's sunset list.  You can find them in the Supported Devices list: https://www.arednmesh.org/content/supported-devices-0

They won't stop working, they just won't support AREDN network traffic that comes from a Babel-only node.   As local areas decide to stop using software versions that include the legacy OLSR routing protocol, those old nodes will just drop off the network.

Hope this helps.

73
Orv W6BI

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer