From: "\"Daniel Roßbach\"" <daniel.rossi@gmx.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] Multipath-Routing BATMAN-ADV
Date: Tue, 15 Jul 2008 09:17:39 +0200 [thread overview]
Message-ID: <20080715071739.175210@gmx.net> (raw)
Hello,
I try to research some possibilities to implement multipath-routing (MPR) to BATMAN Advanced. There are two different ways:
1. one-channel-MPR and 2. multi-channel-MPR.
To the first:
The idea is to use two paths through the mesh and to avoid crossed. I have build a simple model to show that it make sense. The model shows that it can take 67% of the time that needs BATMAN with a single path. I still implemented it into userspace of revision 1060. The next step is to proof, that it works...or that it doesn't work...!
To the second:
The idea is the use of multi paths with multi interfaces. Packets can be transmitted over two different ways without any interference problems. At the moment I'm analyzing the problems and the requirements for this.
The better way is of course the second one. The advantage of using one channel is that there is just one wireless interface needed.
Daniel
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
next reply other threads:[~2008-07-15 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 7:17 "Daniel Roßbach" [this message]
2008-07-16 9:46 ` [B.A.T.M.A.N.] Multipath-Routing BATMAN-ADV Marek Lindner
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=20080715071739.175210@gmx.net \
--to=daniel.rossi@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox