Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juergen Botz <jurgen@botz.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] notes on going for a stable release
Date: Tue, 14 Jan 2014 10:10:04 -0500	[thread overview]
Message-ID: <CAA93jw569n3wD5TMdDaJutVamWPBGRNEKJyCfNbfxThMdqojow@mail.gmail.com> (raw)
In-Reply-To: <52D5292F.40908@botz.org>

On Tue, Jan 14, 2014 at 7:10 AM, Juergen Botz <jurgen@botz.org> wrote:
> On 01/14/2014 03:07 AM, Dave Taht wrote:
>> ** src/dst routing via babels
>>
>>    In the last (3.10.24 dev release I switched to babels from quagga.
>> Either nobody but me uses babel (?), or it "just worked".
>
> I do use it, and it didn't "just work" for me... my second router
> didn't pick up the default route and until reading this just now I
> was still wondering why /etc/quagga disappeared.

I had adopted quagga in the hope of being compatible with
homenet's OSPF direction and being able to use other protocols.

That stuff hasn't made it to quagga yet.

You can, if you prefer, install quagga and the various daemons
with

opkg update
opkg remove babeld
opkg install quagga-vtysh quagga-yourprotocolofchoice

babeld is smaller, and more bleeding edge. I keep hoping
one day to be able to feed per-flow congestion information into it
as a metric....

> On my primary
> /etc/quagga still exists because I did a "keep config" upgrade,
> which obscured matters further because I was looking at the
> wrong config.

Apologies!

Try, during the development process, to never keep a config.

> What should I change on the primary? /etc/babeld.conf or
> /etc/config/babeld?

On your primary router edit:

/etc/config/babeld

and see the first config filter and change it to ignore false

We don't distribute a default route by default (on quagga either!)
because that would lead to routing loops. So distributing a default
route should only happen on gateways to the internet.

The babels code lets you have multiple gateways to the
internet (over ipv6 and natted ipv4), so you can easily have
a network with multiple exit points and still have
it work with real, rather than natted, IPs.

http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases-00

http://tools.ietf.org/html/draft-boutier-homenet-source-specific-routing-00

Support for the src/dst stuff is limited to /etc/babeld.conf at the moment.

>
> :j
>
>



-- 
Dave Täht

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

  reply	other threads:[~2014-01-14 15:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  6:07 Dave Taht
2014-01-14  8:37 ` Christopher Robin
2014-01-14  9:44   ` Toke Høiland-Jørgensen
2014-01-14 12:51     ` David Personette
2014-01-14 13:20       ` Rich Brown
2014-01-14 15:30         ` Dave Taht
2014-01-16  3:20         ` Theodore Ts'o
2014-01-15 15:18   ` Dave Taht
2014-01-14 12:10 ` Juergen Botz
2014-01-14 15:10   ` Dave Taht [this message]
2014-01-14 12:36 ` David Personette
2014-01-15  4:11   ` Dave Taht
     [not found]     ` <CAMybZqzs9ES9G23ke-PjU759wxbQNMytYa4EHmv0H8HqpPwwPQ@mail.gmail.com>
2014-01-15 14:47       ` Dave Taht
2014-01-15  0:30 ` David Lang
2014-01-15 17:31 ` Jim Reisert AD1C
2014-01-20 15:00 ` Maciej Soltysiak
2014-01-20 15:15   ` [Cerowrt-devel] notes on going for a stable release/replacement router Rich Brown

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=CAA93jw569n3wD5TMdDaJutVamWPBGRNEKJyCfNbfxThMdqojow@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jurgen@botz.org \
    /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