Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Benjamin Henrion <bh@udev.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: jp@nexedi.com, cerowrt-devel@lists.bufferbloat.net,
	babel-users@lists.alioth.debian.org
Subject: Re: [Cerowrt-devel] [Babel-users] Lookingfor
Date: Sun, 17 Mar 2013 18:45:38 -0000	[thread overview]
Message-ID: <CANjd3nezBfk=hK+Q+1h09ikOWutORYcHibFkq31ZMqR7oJiw_Q@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6hYc=7Am2KEAj5QhA7HqyNEP2RD9b=Qyw1tg0=nQdD8g@mail.gmail.com>

On Sun, Mar 17, 2013 at 5:35 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Wed, Mar 13, 2013 at 3:34 PM,  <jp@nexedi.com> wrote:
>> Hi,
>>
>>> > There is a budget available in a public institution to sponsor a PhD
>>> > student who would work on babel.
>>>
>>> Do you have a topic in mind?  Who would be the supervisor?  What's the
>>> deadline?
>>
>> Everything can be discussed as long as it helps re6st or SlapOS to achieve further resiliency on enterprise applications.
>>
>> Supervisor would be at ENST.
>>
>> Current ideas:
>> - scalability of babel (1,000,000 nodes network with no backbone)

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

You can run hundreds of babeld inside small openwrt VPSes:

https://github.com/zoobab/openwrt-openvz

You can also use LXC.

>> - ability for public babel network to survive attacks

OLSRd had some encryption key for the packets, don't know for Babel.

About metrics, there was the idea to export infos from the radio layer
(especially from the linux kernel), don't know if this is possible
right now with the latest kernel changes.

--
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-3500762
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."

  reply	other threads:[~2013-03-17 18:45 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 [this message]
2013-03-19 20:28       ` Juliusz Chroboczek
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='CANjd3nezBfk=hK+Q+1h09ikOWutORYcHibFkq31ZMqR7oJiw_Q@mail.gmail.com' \
    --to=bh@udev.org \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jp@nexedi.com \
    /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