> Basic functionality
> *******************
>
> For IPv6, Babel/Quagga should be just as functional as the standalone
> implementation.
>
> For IPv4, you need to have a prefix on your interfaces that covers all
> your neighbours, and the prefixes on all of your interfaces must be
> disjoint.  This is standard practice in traditional networks, but of
> course not in pure meshes.
>
> You can check whether you're bitten by that by typing "show ip route";
> if any of the Babel routes are marked as inactive, that's probably your
> problem.

There are commits in RE-testing-0.99 addressing onlink nexthop management in 
zebra and babeld. The problem should be gone on Linux, could anyone confirm?

-- 
    Denis Ovsienko

_______________________________________________
Babel-users mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users

Reply via email to