From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [B.A.T.M.A.N] OGM problem and documentation
Date: Wed, 4 Jul 2012 12:21:55 +0200 [thread overview]
Message-ID: <20120704102155.GA10503@pandem0nium> (raw)
In-Reply-To: <CAGpqJgoZz+m9d41L2rVtOUzenzue_BjCt+YQ8h_TSEi7QbxwoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]
Hey Arthur,
On Wed, Jul 04, 2012 at 12:00:09PM +0200, Arthur Lambert wrote:
> Hello,
>
> thanks for your answer,
>
> This is what I thought.. Its probably a mistake in my script to
> measure signaling. I will check that.
> I have already read the document that you give to me. This document
> discribes most of the features
> of Batman and some interesting stuffs. But I am looking for
> information about global architecture, how
> the protocol handles threads. An example of usefull draw :
> http://imgur.com/3ecCY. Its not always easy
> to study or understand a complex project like Batman when you does not
> know how a ad-hoc protocol works.
>
> I am trying for example to follow the execution of the module with
> tools like LTTNG to see how works
> the implementation of workqueue or using GCOV to follow the data path.
That's pretty interesting! I don't know if we have something like
an architecture illustration (but haven't see any recently). If you get
anything interesting out of that (illustration, performance insights,
etc), please tell us.
>
> And I interconnect my vm with special way. Its a king of bridge but
> the tool that
> I use simulate network topology so it more complicated than that.
Ah ok. Is it a self-written tool or something public? We usually use
vde/wirefilter to build up different topologies, see:
http://www.open-mesh.org/wiki/open-mesh/Emulation
Would be interesting if there are other possibilities :)
>
> I will come back problably later to ask questions, but at this moment,
> I have to many questions,
> I need first to continue reading the code and twiki, running my tests,
> ... again and again.
Good luck!
Cheers
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-04 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 8:57 [B.A.T.M.A.N.] [B.A.T.M.A.N] OGM problem and documentation Arthur Lambert
2012-07-04 9:20 ` Simon Wunderlich
2012-07-04 10:00 ` Arthur Lambert
2012-07-04 10:18 ` Marek Lindner
2012-07-04 10:21 ` Simon Wunderlich [this message]
2012-07-04 12:05 ` Arthur Lambert
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=20120704102155.GA10503@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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