[Babel-users] Restarting MeshPoint – seeking advice on routing for crisis/disaster scenarios
Henning Rogge
hrogge at gmail.com
Thu Dec 18 09:49:56 GMT 2025
On Thu, Dec 18, 2025 at 1:49 AM Juliusz Chroboczek <jch at irif.fr> wrote:
> > I know that in active conflict zones Wi-Fi can be jammed
>
> The nice thing about having a layer 3 routing protocol is that you can
> combine technologies: Babel is designed to handle a network that has both
> wired and wireless links, and that uses multiple wireless technologies at
> the same time (WiFi at various frequencies, UWB, infrared laser, etc.).
> In such a network, Babel should be able to find a path consisting of
> whichever links are not jammed at a given time.
>
> Of course, this assumes that the opponent is not able to jam all links
> simultaneously.
If you expect malicious jamming you might want to spend some more
brainpower into your routing metric... to make sure you prefer stable
links over good but unstable ones... otherwise the "enemy" will just
jam you in pulses and kill your network by constant routing updates.
> > - BATMAN-adv-style seamless mobility
>
> I started working on sroamd[1], which implements seamless mobility at
> layer 3, but then Covid happened, and I got interested in
> videoconferencing. I guess we could revive it if there's interest.
>
> [1]: https://github.com/jech/sroamd
>
> > - Better large-scale behaviour for hundreds-to-thousands of nodes in
> > sparse or battery-constrained setups
>
> Could you please clarify?
Yeah, scalability is always an issue, especially in networks with
changing conditions (e.g. hostile jamming).
Henning Rogge
More information about the Babel-users
mailing list