[Babel-users] Babel for Quagga status

[Juliusz Chroboczek]

>> 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.

> 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?

Confirmed -- it works.  Denis, that's great -- I had tried to fix that
myself on a few occasions, but it turned out I'm not competent.

I'm attaching the output of "show ip route" on huponomos.  You'll notice
that the interfaces alpha, beta and gamma have the same local address --
we're in a pure mesh network, so there's no connected prefix (or, if you
prefer, it's a /32).

Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, A - Babel,
       > - selected route, * - FIB route

    K>* 0.0.0.0/0 via 134.157.168.126, eth0
    A>* a.b.c.d/32 [95/0] via e.f.g.h, coloquinte, onlink, 00:01:05
    A>* e.f.g.h/32 [95/0] via e.f.g.h, coloquinte, onlink, 00:01:05
    C>* 127.0.0.0/8 is directly connected, lo
    K * 134.157.168.0/25 is directly connected, eth0
    C>* 134.157.168.0/25 is directly connected, eth0
    C>* 192.168.1.0/24 is directly connected, eth0
    C * 192.168.4.20/32 is directly connected, gamma
    C * 192.168.4.20/32 is directly connected, beta
    C * 192.168.4.20/32 is directly connected, alpha
    C>* 192.168.4.20/32 is directly connected, coloquinte
    A>* 192.168.4.25/32 [95/0] via 192.168.4.25, alpha, onlink, 00:01:05
    A>* 192.168.4.27/32 [95/0] via 192.168.4.25, alpha, onlink, 00:01:05
    A>* 192.168.4.30/32 [95/0] via 192.168.4.25, alpha, onlink, 00:01:05
    A>* 192.168.4.31/32 [95/0] via 192.168.4.25, alpha, onlink, 00:01:05
    A>* 192.168.4.33/32 [95/0] via 192.168.4.25, alpha, onlink, 00:01:05
    R>* 192.168.5.0/24 [120/2] via 134.157.168.57, eth0, 00:01:19

-- Juliusz