public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "P. Mazart" <pmazart@web.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.] Hiding Local Topology ??? TTL
Date: Wed, 11 Mar 2009 14:20:49 +0100	[thread overview]
Message-ID: <200903111420.49535.pmazart@web.de> (raw)
In-Reply-To: <20090305135831.GA1563@WGT634U>

Hello again,

Am Donnerstag, 5. März 2009 schrieb Sven Eckelmann:
> Please read http://open-mesh.net/wiki/BranchesExplained to understand
> basic differences between the "brands".

Ok did it.
Obviously "batman" stands for an algorithm on one hand and 
implementation on the other hand… 
Can you say why there are different userspace-implementations and what 
their difference is? („Experimental is not Debian“ is what I know, yet.)

> If you would really compare batman-adv-kernelland and batmand then
> please ask again - I don't have any good numbers here, but maybe
> somebody else has.

Yes, I thought there might be differences due to the translation (e.g.) 
to sockets inside the kernel when using batmand or something.

But as far as got to know now the originatorpacketsize of batmand 
(≈60bytes) is small compared to the sizes of olsr's anyway. (≈500bytes 
with 300 nodes(?))

Thanks for your help
P.M.

  reply	other threads:[~2009-03-11 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 20:26 [B.A.T.M.A.N.] Hiding Local Topology – TTL P. Mazart
2009-03-05 10:55 ` P. Mazart
2009-03-05 11:14   ` Marek Lindner
2009-03-05 13:22     ` P. Mazart
2009-03-05 13:29       ` P. Mazart
2009-03-05 13:58       ` [B.A.T.M.A.N.] Hiding Local Topology ??? TTL Sven Eckelmann
2009-03-11 13:20         ` P. Mazart [this message]
2009-03-11 21:51           ` Sven Eckelmann
2009-03-11 22:09             ` P. Mazart

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=200903111420.49535.pmazart@web.de \
    --to=pmazart@web.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