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] RTT-based metric merged
Date: Fri, 16 May 2014 18:30:38 -0700	[thread overview]
Message-ID: <CAA93jw7qTRLowr1QGZkcyN5Y5heF80RyHWjNJ2K7ZFZbPCvMXg@mail.gmail.com> (raw)
In-Reply-To: <7ippjdeg91.wl%jch@pps.univ-paris-diderot.fr>

Juliusz waited evilly until I got towards thinking we had a stable
release process...

We've had source specific routing in place for a while...

http://arxiv.org/pdf/1403.0445v1.pdf

Now there's an RTT sensitive metric.

---------- Forwarded message ----------
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Date: Fri, May 16, 2014 at 11:21 AM
Subject: [Babel-users] RTT-based metric merged
To: babel-users@lists.alioth.debian.org


Dear all,

I've just merged into master Baptise Jonglez's work that implements an
RTT-based metric for Babel.  This is described in detail on

  http://arxiv.org/pdf/1403.3488v1.pdf

In short, this change enables using RTT in order to choose between
"good" and "bad" tunnels.  It is disabled by default, and can be
enabled by doing

  interface tun-42 enable-timestamps true

In order for it to be useful, you need to enable it on both sides of
the tunnel.  You can tune the parameters of the metric with the
rtt-min, rtt-max ans max-rtt-penalty parameters.

Any feedback will be warmly welcomed before I release 1.5.0, and
received with undisguised hostility after that.

-- Juliusz

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


-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

           reply	other threads:[~2014-05-17  1:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <7ippjdeg91.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=CAA93jw7qTRLowr1QGZkcyN5Y5heF80RyHWjNJ2K7ZFZbPCvMXg@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