> Given a a bunch of OpenWRTrouters running babel - what are the ideas /
> best practices for integrating non-mesh client?
It is a difficult problem.
There are two competing models:
1. Every Babel router has two interfaces -- one in ad-hoc mode, that runs
Babel, and one in AP mode, that runs a D
Instead of adding a covering route, and explicitly denying other
routes from being distributed,
would it be possible to have a smarter filter with syntax like
"redistribute local prune"
That would cut something like this down from:
2601:696:8300:2cb0:dc9f:abff:fe06:1a24 via fe80::28c6:8eff:febb:
2 matches
Mail list logo