From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org,
Patrick Bosch <patrick.d.bosch@googlemail.com>
Subject: Re: [B.A.T.M.A.N.] How to read batadv-vis jsondoc correctly
Date: Fri, 27 May 2016 13:57:31 +0200 [thread overview]
Message-ID: <1623525.LPZfOt2ObD@prime> (raw)
In-Reply-To: <mailman.211.1463472563.23655.b.a.t.m.a.n@lists.open-mesh.org>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hi Patrick,
sorry for the late reply.
On Tuesday 17 May 2016 10:09:27 Patrick Bosch via B.A.T.M.A.N wrote:
> Hi all
>
> As the title suggest, I'm wondering how to read the jsondoc output
> correctly. It seems that every possible link is included in that
> output, but which one is the one that is used? If there is one link,
> it should be the one with the lowest metric, but what if a node has
> more than one link?
>
> For example the following setup:
>
> Node 1
> |
> |
> Node 2 ------- Node 3
>
> Here, node two would have two links. Now, if there would be some more
> nodes that are in the jsondoc output, how can I find out which are the
> links that are in use?
The nodes which appear in the jsondoc are only originators which batman-adv
decided to reach directly (with one hop) - so these are direct neighbors.
Basically, all of these links would be in use from one node to its neighbor,
so all of them are "in use". But you can't find out how much a link is
actually used (i.e. how many packets/bytes are transmitted), or which neighbor
is used to reach a distant neighbor.
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2016-05-27 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.211.1463472563.23655.b.a.t.m.a.n@lists.open-mesh.org>
2016-05-27 11:57 ` Simon Wunderlich [this message]
2016-05-30 14:14 ` [B.A.T.M.A.N.] How to read batadv-vis jsondoc correctly Patrick Bosch
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=1623525.LPZfOt2ObD@prime \
--to=sw@simonwunderlich.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=patrick.d.bosch@googlemail.com \
/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