From: elektra <onelektra@gmx.net>
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: Mon, 27 Apr 2009 18:44:03 +0200 [thread overview]
Message-ID: <49F5E0D3.208@gmx.net> (raw)
In-Reply-To: <209743CECB91EB4F84169A51F300410D1F3137C3F9@MAIL02.ug.kth.se>
Hello Vojislav!
I have a personal wish list of things that would be great to have in
Batman. I don't know if any of these would be suitable/interesting for
you, but I will use the opportunity to post it to the list now:
* Modify Batman-0.3.X in order to support IPv6
* Improve Batman with regards to protocol overhead and convergence speed
* Get support for other operating systems working (so far it only works
with Linux)
* Implement a minimalistic and power saving Batman client version for
embedded mobile devices
* 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)
Cheers,
elektra
> Hi!
>
> My name is Vojislav Marinkovic and I am a student of Electrical Engineering at the Royal Institute of Technology in Stockholm. My major is Communication Networks and right now I am looking for an interesting subject for my masters thesis. While browsing the Internet for some interesting topics, I ran into your project which is very similar to (yet better than) one of my own ideas. So I thought "why should I put time on inventing wet water instead of joining the project?",
>
> 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. (I'm not suggesting anything, but as an example let's say potential issues with live streaming over a B.A.T.M.A.N.-network), comparing B.A.T.M.A.N. some other routing protocol/s or any other topic related to my major subject. I really don't have any idea on what problems you have encountered so please help me find a good topic for my masters thesis.
>
> The thesis will be done during this summer.
>
> Thank you in advance
> Vojislav Marinkovic
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://lists.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
>
next prev parent reply other threads:[~2009-04-27 16:44 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 [this message]
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
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=49F5E0D3.208@gmx.net \
--to=onelektra@gmx.net \
--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.