From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Masters thesis
Date: Wed, 29 Apr 2009 10:59:45 +0800 [thread overview]
Message-ID: <200904291059.45857.lindner_marek@yahoo.de> (raw)
In-Reply-To: <209743CECB91EB4F84169A51F300410D1F3137C3F9@MAIL02.ug.kth.se>
Hi,
> On your homepage you stated that you have a lot of ideas but you don't have
> the time to implement them all. My question is, do you have any ideas that
> would fit to be done as a masters thesis in communication networks? It
> could be anything from an issue related to the protocol itself or it could
> be porting an already deployed technology on other types of networks to the
> B.A.T.M.A.N.
welcome on board. :-)
I'm very happy that you ask. Elektra already suggested a few things. I'm going
to extend this list and group it a bit to outline the focus of the
corresponding tasks. That should give you a good starting point.
I suggest you choose your candidates out of these before we dive into the
details. Then you will have an idea what to expect and you can make a decision
whether you want to do it. :-)
one afternoon of work (at maximum):
* Modify Batman-0.3.X code so we have an option to compile it without
policy routing support
* Modify the way that Batman-Advanced (Layer 2) deals with
broadcast/multicast payload packages (on multihop wireless routes there
is always packet loss, protocols like DHCP use broadcast or multicast
messages which are not send redundantly and not acknowledged, so these
protocols which are not designed to deal with a high level of packetloss
have difficulties to work on a Layer 2 mesh as the number of hops and
packet loss on the media increases)
several weeks of coding effort (including tests):
* Modify Batman-0.3.X in order to support IPv6
* Get support for other operating systems working (so far it only works
with Linux) -> depends on your knowledge of "other" systems
* merge batman adv userspace & kernelland code to reduce the maintenance
overhead
* automatic interface bonding for better throughput (layer 2)
requires in depth knowlegde about batman:
* Improve Batman with regards to protocol overhead and convergence speed
mt. everest:
* Implement a minimalistic and power saving Batman client version for
embedded mobile devices (requires extensive knowledge of 802.11 power saving
mechanisms and how to bring them into the mesh)
* multipath routing (as it always appears over and over again:
http://en.wikipedia.org/wiki/Multipath_routing)
Regards,
Marek
next prev parent reply other threads:[~2009-04-29 2:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 14:42 [B.A.T.M.A.N.] Masters thesis Vojislav Marinkovic
2009-04-27 16:44 ` elektra
2009-04-27 17:41 ` Vojislav Marinkovic
2009-04-30 8:24 ` Maik Wodarz
2009-04-30 8:46 ` Marek Lindner
2009-04-30 11:41 ` elektra
2009-04-29 2:59 ` Marek Lindner [this message]
2009-05-01 10:51 ` Vojislav Marinkovic
2009-05-01 15:11 ` elektra
2009-05-01 15:32 ` Troy Benjegerdes
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200904291059.45857.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.