Hey Folks, Is there a way to query the babel protocol in AREDN ? I would normally just use vtysh in conjunction with FRR, but that isn't available here.
Here's what an AI had to say about getting babel status in an AREDN environment:
On AREDN you mostly use the web UI for status, plus a few SSH commands to look directly at the Babel daemon and routing tables.
From the AREDN web UI
On any 3.25.x or later build with Babel enabled:
• “Mesh status” / “Local mesh status” page: shows nodes currently reachable via Babel.
• Topology / neighbor panels: show which nodes are neighbors and how they are reached.
These are the quickest checks that “Babel is up and routing.”
Via SSH shell on the node
SSH to the node and then:
• logread | grep babel – confirm the Babel daemon has started cleanly and see any error messages.
• ip -4 route and ip -6 route – see what routes actually made it into the kernel; Babel-learned routes will appear here if they are active.
• ip neigh – check link‑local neighbours on the RF and DtD/tunnel interfaces; useful to confirm layer‑2/3 connectivity when Babel routes are missing.
AREDN hides most of the babeld CLI by design, so you normally don’t have direct babeld control-socket commands on production images.
On AREDN you mostly use the web UI for status, plus a few SSH commands to look directly at the Babel daemon and routing tables.
From the AREDN web UI
On any 3.25.x or later build with Babel enabled:
• “Mesh status” / “Local mesh status” page: shows nodes currently reachable via Babel.
• Topology / neighbor panels: show which nodes are neighbors and how they are reached.
These are the quickest checks that “Babel is up and routing.”
Via SSH shell on the node
SSH to the node and then:
• logread | grep babel – confirm the Babel daemon has started cleanly and see any error messages.
• ip -4 route and ip -6 route – see what routes actually made it into the kernel; Babel-learned routes will appear here if they are active.
• ip neigh – check link‑local neighbours on the RF and DtD/tunnel interfaces; useful to confirm layer‑2/3 connectivity when Babel routes are missing.
AREDN hides most of the babeld CLI by design, so you normally don’t have direct babeld control-socket commands on production images.
There's also 'babel-dump.
Hope that helps.
Orv W6BI