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"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Babel-users] ANNOUNCE: babeld-1.6.0
Date: Tue, 14 Apr 2015 08:46:15 -0700	[thread overview]
Message-ID: <CAA93jw7BVFo0pXFmjTV76nC+BoeT6c+VhHHirm6qXt3BLjx6RA@mail.gmail.com> (raw)
In-Reply-To: <87pp76ew8l.wl-jch@pps.univ-paris-diderot.fr>

[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]

It looked to me as if ipv6_subtrees was now a configure option. All
our kernels (since 3.10.12) and most (probably all) distro kernels,
enable ipv6_subtrees.

I am happy to see this code finally merged, as the mainline daemon
also has support for the long-rtt metric extension, and this takes the
current fork of the babeld and babels packages in openwrt and merges
them back together into one. (not clear if that happened yet, I have
only been awake a few minutes).

https://tools.ietf.org/html/draft-jonglez-babel-rtt-extension-00

I hope this summer to be able to explore the "rtt as a routing metric"
idea on shorter rtts in the context of having fq_codel everywhere and
per-sta queues for wifi. It may require higher precision than is
currently obtained in the code (does not use the SO_TIMESTAMP socket
option in particuar) however.

I wrote up the potential benefits of using delay as a metric on this
thread here:

http://lists.alioth.debian.org/pipermail/babel-users/2015-April/001974.html


---------- Forwarded message ----------
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Date: Tue, Apr 14, 2015 at 5:21 AM
Subject: [Babel-users] ANNOUNCE: babeld-1.6.0
To: babel-users@lists.alioth.debian.org


Dear all,

I am happy to announce that babeld-1.6.0 is available from

  http://www.pps.univ-paris-diderot.fr/~jch/software/files/babeld-1.6.0.tar.gz
  http://www.pps.univ-paris-diderot.fr/~jch/software/files/babeld-1.6.0.tar.gz.asc

For more information about babeld and the Babel routing protocol, please see

  http://www.pps.univ-paris-diderot.fr/~jch/software/babel/

The main news in this version is that source-specific routing is part of
the stock babeld daemon.  This is a large change, and is due to Matthieu
Boutier.  For more information about source-specific routing, please see

  Matthieu Boutier and Juliusz Chroboczek.
  Source-specific routing.
  To appear in Proc. IFIP Networking 2015.
  http://arxiv.org/pdf/1403.0445

Enjoy,

-- Juliusz Chroboczek



_______________________________________________
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users


-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

[-- Attachment #2: Type: application/pgp-signature, Size: 484 bytes --]

           reply	other threads:[~2015-04-14 15:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87pp76ew8l.wl-jch@pps.univ-paris-diderot.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=CAA93jw7BVFo0pXFmjTV76nC+BoeT6c+VhHHirm6qXt3BLjx6RA@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