Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Benjamin Henrion <bh@udev.org>
Cc: babel-users@lists.alioth.debian.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Babel-users] Lookingfor
Date: Tue, 19 Mar 2013 20:28:41 -0000	[thread overview]
Message-ID: <7ippyvgmmq.wl%jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CANjd3nezBfk=hK+Q+1h09ikOWutORYcHibFkq31ZMqR7oJiw_Q@mail.gmail.com>

> You will have to change babeld to only consider a slice of the network.

Manual aggregation can be done without changing anything.  On a border
router for the network 192.168.42.0/24, you say

  ip route add unreachable 192.168.42.0/24 proto static

and in babeld.conf,

  out ip 192.168.42.0/24 ge 25 deny

For reliability, you should also add some filtering rules to avoid
leaking local routes into the other subnets.

Automatic aggregation would be possible with just some minor changes
to the implementation (not the protocol), but deaggregation would need
to trigger a (user-configurable) hold time to avoid transient routing
loops.  (That's okay, though, deaggregation should never happen in
a well-designed network -- if you cannot guarantee that your border
routers are stable, you deserve the hold time.)

-- Juliusz

  reply	other threads:[~2013-03-19 20:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r4jjkvld.wl%jch@pps.univ-paris-diderot.fr>
     [not found] ` <20130313223423.7567EBF0037@mail2.tiolive.com>
2013-03-17 16:35   ` Dave Taht
2013-03-17 18:45     ` Benjamin Henrion
2013-03-19 20:28       ` Juliusz Chroboczek [this message]
2013-03-19 10:20     ` Toke Høiland-Jørgensen
2013-03-19 12:20       ` jp
2013-03-19 20:13     ` Juliusz Chroboczek

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=7ippyvgmmq.wl%jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.univ-paris-diderot.fr \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=bh@udev.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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