Hi, myself and Justin Kilpatrick have done a lot of this kind of stuff, and
Docker is kind of a distraction IMO. You're better off using raw network
namespaces. Here's a script we made to generate virtual networks with
configurable packet loss and latency from a json config format:
Unfortunately there's a paywall on that article, but I was wondering, what
advantages does their queue aware technique have over latency based routing?
On Tue, Sep 26, 2017 at 1:01 PM, Dave Taht wrote:
> I too may be able to visit Paris in late march.
>
> also, a start at
I'm wondering... what if, in the hypothetical routing protocol "Babble",
one got rid of multicast hellos and ETX entirely, and routed using RTT
measured by unicast hellos. Wouldn't this take delays from ARQ'ed packet
loss into account have results somehow similar to ETX?
On Tue, Jun 20, 2017 at
Forwarding these Battlemesh testbed results. Looks like Babel did ok.
-- Forwarded message --
From: Leonardo Maccari
Date: Tue, Jun 13, 2017 at 5:54 AM
Subject: Report on the testbed results
To: battlemesh
Dear battlemeshers,
Here
Got it working, thanks for the help
On Tue, Jun 6, 2017 at 9:26 PM, Gabriel Kerneis <gabr...@kerneis.info>
wrote:
> On Tue, Jun 6, 2017, at 20:41, Jehan Tremback wrote:
>
> No, our only way to configure nodes for any given protocol is a shell
> script. I could make it write
No, our only way to configure nodes for any given protocol is a shell
script. I could make it write out a file, but I was trying to keep it
simple. Would a file help?
On Tuesday, June 6, 2017, Gabriel Kerneis <gabr...@kerneis.info> wrote:
> On Tue, Jun 6, 2017, at 19:00, Jehan Tremb
Hi everyone, I volunteered to set up babeld for the Battlemesh testbed,
since nobody else was going to do it. The testbed consists of some 2.4/5ghz
wifi routers. The 2.4ghz radio is used for management, while the 5ghz radio
runs the protocol being tested.
Each routing protocol needs to have a
Hello everybody,
I'm doing some experiments. I would like to be able to give babeld an IP
address and have it send Hellos to the address (whether or not it is a
neighbor). I would also like to make sure that nodes are able to respond to
such non-neighbor Hellos with IHUs. I would then like to
What is your goal?
On Sun, Oct 23, 2016 at 5:09 AM, andri warda wrote:
> Hello, i want to ask how to implement babel with hmac ?
> I read the paper but i didn't find the steps how to implement that.
> Please answer my question. Thank you
>
>
I might be interested in participating in IETF 96. Are there more details
about how much it costs etc.? How much of the event will be Babel-related?
-Jehan
On Sun, Jun 19, 2016 at 5:00 AM, <
babel-users-requ...@lists.alioth.debian.org> wrote:
> Send Babel-users mailing list submissions to
>
Someone posted in April that they were working on a Golang implementation
of Babel. Does anyone know where the code for that is located?
-Jehan
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
Sorry, the diagram should be:
(A)--2--(B)--3--(C)--1--(D) = 6
(A)--5--(D) = 6
On Mon, May 23, 2016 at 7:28 PM, Jehan Tremback <jehan.tremb...@gmail.com>
wrote:
> We are trying to mitigate one of the issues described in RFC6126:
>
> > As defined in th
We are trying to mitigate one of the issues described in RFC6126:
> As defined in this document, Babel is a completely insecure protocol. Any
attacker can attract data traffic by advertising routes with a low metric.
We're concerned about this mostly because a node could advertise a low
metric,
This is more a theoretical than practical question right now, but is it
possible for a node to verify the ETX metrics of its neighbors? That is,
compute the ETX between myself and a given destination, and use it to
confirm that the additive ETX metric to that destination computed by the
neighbor
14 matches
Mail list logo