From: Dave Taht <dave.taht@gmail.com>
To: Denis Ovsienko <infrastation@yandex.ru>
Cc: babel-users <babel-users@lists.alioth.debian.org>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Babel-users] Babel for Quagga status
Date: Mon, 18 Jun 2012 12:00:13 -0400 [thread overview]
Message-ID: <CAA93jw66nB_87yv5c28H-u5BzrKrGTxWyckvDi678CuwruQa2A@mail.gmail.com> (raw)
In-Reply-To: <238931340020488@web16d.yandex.ru>
On Mon, Jun 18, 2012 at 7:54 AM, Denis Ovsienko <infrastation@yandex.ru> wrote:
>
>> 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?
I have put this version of quagga-re into the Ceropackages-3.3
repository for openwrt, which I keep on github. It does compile, but
I'm not in a position to test right now. Ceropackages can be added to
any given openwrt feed, and built for any target (hint, hint)
However I did put these new quagga binary packages for the wndr3700v2
and wndr3800 up with a very "testy" cerowrt release (with some
problems that I need to resolve before making a build more widely
available ! notably a firewall issue or three )
They are on my dev box at:
http://snapon.lab.bufferbloat.net/~cero1/3.3/3.3.8-4/
I'm *delighted* to see this fix as well as the cool new authentication code.
--
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/
parent reply other threads:[~2012-06-18 16:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <238931340020488@web16d.yandex.ru>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw66nB_87yv5c28H-u5BzrKrGTxWyckvDi678CuwruQa2A@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=infrastation@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox