Hi,
Babeld 0.97 is available on
http://www.pps.jussieu.fr/~jch/software/files/babeld-0.97.tar.gz
http://www.pps.jussieu.fr/~jch/software/files/babeld-0.97.tar.gz.asc
The config and log files have been renamed to babeld. Other than that,
there's only a minor reworking of the command-line par
>> ok, I've done with you suggest, I also ran babel-pinger -p 42.
> No, run babel-pinger normally (protocol and table are orthogonal).
That's the point with 42: it's the answer to everything, but not to
anything. Mysterious magic number...
--
Gabriel
___
> ok, I've done with you suggest, I also ran babel-pinger -p 42.
No, run babel-pinger normally (protocol and table are orthogonal).
> I'm not getting the second default route from the A router on the
> B router.
> r...@grant:~# ip route show
ip route show table 42
ok, I've done with you suggest, I also ran babel-pinger -p 42. I'm
not getting the second default route from the A router on the B
router.
I suppose I am looking for something like "default via 10.38.8.1 dev
eth0.1 proto 42" on router B.
On both routers the babel.conf looks like:
redistribute lo
Should I still be running babel-pinger in this case?
On Thu, Nov 5, 2009 at 20:59, Juliusz Chroboczek
wrote:
> I think that the proper solution is to use multiple routing tables, one
> for the DHCP route and one for Babel; this way, your node will have both
> default routes at the same time, but
I think that the proper solution is to use multiple routing tables, one
for the DHCP route and one for Babel; this way, your node will have both
default routes at the same time, but prefer the Babel route to the DHCP
route.
Add something like this to your init scripts:
ip rule add prio 100 tabl
In fact, it's just:
AB-
A solution I see might be to modify babel itself to give it more
control over these external routes. I was hoping babel-pinger would
help manage this but now I more fully understand what it does and this
is not it's role.
I started writing a script to repl
7 matches
Mail list logo
