From: Freifunk Dresden <freifunk@ddmesh.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.] routing / direct connection
Date: Tue, 25 Sep 2007 10:06:02 +0200 [thread overview]
Message-ID: <46F8C16A.1010805@ddmesh.de> (raw)
In-Reply-To: <200709212038.41280.axel@open-mesh.net>
Hi,
I shortly checked your writing and found some unclear points.
- What is the difference (-d 1 ) of the viaIF and the viaIF of
the optional info block?
- the nlq = l2q / l2: what is l2?
- you compare the lq with the OLSR-ETX. But can you explain it
without "OLSR-ETX", because I don't like to check the documentation
of OLSR
-bidirectional timeout: is the number given in seconds or sequence count difference
or something other?
If haven't already planed, the options --dups-xxx --asymmetric-xxx and all
that only have the blue bar needs more description and what influence they have
within the batmand. Examples as you have offered by --window-size are very
helpful.
Regards
Stephan
next prev parent reply other threads:[~2007-09-25 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 12:37 [B.A.T.M.A.N.] routing / direct connection Freifunk Dresden
2007-09-21 18:38 ` Axel Neumann
2007-09-25 8:06 ` Freifunk Dresden [this message]
2007-09-25 11:26 ` Axel Neumann
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=46F8C16A.1010805@ddmesh.de \
--to=freifunk@ddmesh.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.