From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] babeld change
Date: Sun, 16 Jun 2013 14:55:56 -0700 [thread overview]
Message-ID: <CAA93jw6Up+t6BqReqPReWM+xarNfkngVqvue_+bV9Y3GH=1fKg@mail.gmail.com> (raw)
In-Reply-To: <87ip1dpw2y.fsf@toke.dk>
On Sun, Jun 16, 2013 at 2:47 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Dave Taht <dave.taht@gmail.com> writes:
>
>> There is a lot of interesting work coming up on babel, and I've not
>> got around to trying to merge the homenet work into quagga. I am
>> thinking of switching back (at least temporarily) to the standalone
>> babeld daemon rather than quagga-babeld to test out the algorithms
>> there. Any objections?
>
> Fine with me; I've been exclusively running the standalone babeld. Note
> that the new multi-wan IPv6 stuff makes babel not pick up the default
Hmm. Does this mean you have 6in4 working correctly in your build of
cero? I'm still just doing it with a script, not netifd.
> routes for ipv6 unless you add extra import_table statements. My
> /etc/config/babel has this in it:
>
> config general
> option 'conf_file' '/etc/babeld.conf'
> list 'import_table' '254'
> list 'import_table' '1007'
>
> The last value might vary depending on the setup; not sure how the table
> names are generated by netifd, but it's been quite stable on my device
> at 1007.
Hmm. We're back at wanting a message bus or std kernel api for dealing
with the ip rule database again... I fear that things like openvpn or
strongswan will really mess with this.
> There's a patch for babeld to support this in ceropackages, but if
Babel head has three branches doing new stuff. In particular, the
configuration syntax is changing in some respects...
hah. I just realized that a couple of the commits in babeld head were
yours. cool. no need for me to lecture.
One thing that always bugged me about previous versions of babeld was
that it didn't chomp whitespace at the end of a line, hopefully that's
fixed somewhere in this patch series...
> you're going to go to newest git it should have been merged upstream.
> The init script in ceropackages is patched to support this syntax;
> haven't gotten that upstreamed to openwrt iirc...
While I'm at it I note that robert bradley's attempt at atomic route
updates for babel appears to fail on 3.10rc3 on x86, leaving behind
routes, and or leaving behind permanently unreachable ones. Sigh.
>
> -Toke
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-06-16 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 21:15 Dave Taht
2013-06-16 21:47 ` Toke Høiland-Jørgensen
2013-06-16 21:55 ` Dave Taht [this message]
2013-06-16 22:04 ` Toke Høiland-Jørgensen
2013-06-16 22:08 ` [Cerowrt-devel] Field Report - installing 3.8.13-7 Rich Brown
2013-06-16 22:29 ` Toke Høiland-Jørgensen
2013-06-16 22:35 ` Dave Taht
2013-06-16 22:54 ` Rich Brown
2013-06-17 8:24 ` Toke Høiland-Jørgensen
2013-06-17 4:15 ` [Cerowrt-devel] babeld change Steven Barth
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='CAA93jw6Up+t6BqReqPReWM+xarNfkngVqvue_+bV9Y3GH=1fKg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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