Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: [Babel-users] babeld/quagga: v4 and v6 distribution
Date: Thu, 20 Sep 2012 06:36:04 -0700	[thread overview]
Message-ID: <CAA93jw6RavPSOqCSi34kERK0fqO0ROXvqay=NsvtQ11zhRe9hA@mail.gmail.com> (raw)
In-Reply-To: <9E40B905-6124-454E-B2CF-6BDC3239EB4C@pps.jussieu.fr>

This enhancement to quagga (which is in cerowrt-sugarland) adds back
an ability we lost in converting from the original babeld.

I used it to allow ipv6 traffic to be routed over ipv4 natted links in
the bloatlab. (by blocking ipv4 distribution over the shared external
wire but allowing ipv6) No doubt there are other uses.

One of my thoughts with this technology is to be able to share your
ipv6 routes/addresses with your neighbor, be your ipv6 connection be
native or tunnelled.

---------- Forwarded message ----------
From: Matthieu Boutier <boutier@pps.jussieu.fr>
Date: Sun, Sep 16, 2012 at 3:27 PM
Subject: [Babel-users] babeld/quagga: v4 and v6 distribution
To: babel-users@lists.alioth.debian.org


Hello,

It's now possible to distribute both v4 and v6 on quagga's babeld in
quagga RE-testing-0.99, but the syntax is affected.

The definition of an access/prefix-list doesn't differ: the kind (v4
or v6) is explicit, e.g. :
access-list toto deny any
ipv6 access-list toto deny any
(note that you have in this example the same name ("toto") for two
different lists: one v4, the other v6)

You must specified v4 or v6 for the redistribution:
distribute-list toto  /* will distribute the v4 "toto" list */
ipv6 distribute-list toto  /* will distribute the v6 "toto" list */

For ripng, which use only v6, you can continue to use the v4 syntax :
distribute-list toto /* will distribute the v6 list */
ipv6 distribute-list toto /* same */

Here is a complete example:

password zebra
enable password zebra

router babel
  network eth0
  distribute-list global_ipv4 in eth0
  distribute-list local_ipv4 out eth0
  ipv6 distribute-list local_ipv6 out eth0
  redistribute kernel
  redistribute connected
  redistribute static
  redistribute ripng

access-list local_ipv4 permit 1.2.3.0/23
access-list local_ipv4 deny any

access-list global_ipv4 deny 1.2.0.0/16
access-list global_ipv4 permit any

ipv6 access-list local_ipv6 permit 2001:2:3:4::/64
ipv6 access-list local_ipv6 deny any

log file /var/log/quagga/babeld.log

--
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
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

           reply	other threads:[~2012-09-20 13:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <9E40B905-6124-454E-B2CF-6BDC3239EB4C@pps.jussieu.fr>]

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='CAA93jw6RavPSOqCSi34kERK0fqO0ROXvqay=NsvtQ11zhRe9hA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --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