[Cerowrt-devel] Fwd: [Babel-users] ANNOUNCE: Babel-S update

[Dave Taht <dave.taht@gmail.com>]

I have longed for the source specific functionality for several
reasons. I am sore tempted to replace quagga with this version of
babeld because:

0) homenet compatible patches for quagga ospf haven't been merged yet
1) I would like to test ipv6 native, 6rd, and several forms of tunnel
at the same time. babels will let me do this
2) the mptcp congestion control problem is fascinating

Is there anyone using quagga's other routing protocols currently and
can't live without being able to add in ripd, bgp, or ospf?



---------- Forwarded message ----------
From: Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>
Date: Sat, Dec 14, 2013 at 2:31 AM
Subject: [Babel-users] ANNOUNCE: Babel-S update
To: babel-users@lists.alioth.debian.org


Dear all,

There is many changes in the source-sensitive version of babeld
since the last announce. Recall that the code is available at:

    git clone -b source-specific
git://git.wifi.pps.univ-paris-diderot.fr/babels.git
    http://git.wifi.pps.univ-paris-diderot.fr/?p=babels.git
    https://github.com/boutier/babeld

CHANGES:

- configuration:

    - filter: you can filter source-specific routes using "src-ip", "src-eq",
        "src-le", "src-ge".  It works as "ip", "eq", etc.

    - importing specific routes: now, this is done via filters.  Instead of
        using "allow", just use "src-specific <prefix>".  This can be done
        either in the "redistribute" or "in" filters.

        For example, in order to redistribute all v4 routes as specific to
        192.268.1.0/24, use

            redistribute src-specific 192.168.1.0/24

        Be worry when using it in the "in" filter... You will found details and
        more examples in the manpages.

- implementation:

    - IPV6-SUBTREES: Since Linux 3.10.12, source-sensitive routing tables can be
        used as we expected.  If you compile the code with '-D IPV6_SUBTREES',
        it will use the native netlink API instead of using multiple routing
        tables with rules over it.  Of course, the IPv4 part of the code is let
        unchanged.

        The best solution would be to check it dynamically.  If someone knows
        how to do that...

    - requests: Source-specific request messages are implemented.

- other:

    Many bugs have been fixed, especially for the interoperability and TLV
    compression mechanism.

Best regards,
Matthieu


_______________________________________________
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html