From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Janne Paatero <janne.paatero@ruag.com>
Subject: Re: [B.A.T.M.A.N.] Alfred batadv-vis json conformance
Date: Thu, 3 Oct 2013 10:53:16 +0200 [thread overview]
Message-ID: <20131003085316.GB20056@lunn.ch> (raw)
In-Reply-To: <20131003082221.GC1939@neomailbox.net>
> > But how do we determine the algorithm version? For the moment it can
> > simply be hard coded. But for version 5? Will the over-alfred format
> > change? Will we have a "struct vis_v2" and VIS_PACKETVERSION_2 for
> > algorithm 5?
>
> Good question. Maybe we don't really need to export the algorithm version?
>
> In the end this information can be retrieved on the _same_ node where alfred (&
> vis) is running by reading the "routing_algo" (sysfs-)file.
No, that does not work. You can run alfred on a machine without
BATMAN. alfred --help says:
server mode options:
-i, --interface specify the interface to listen on
-b specify the batman-adv interface configured on the system (default: bat0)
use 'none' to disable the batman-adv based best server selection
I'm using this "-i eth0 -b none" since my network topology has the
logger on a machine which is bridged into the mesh.
> What about the source version? How did you get it from the module?
It is the alfred version, not the kernel module version.
Andrew
next prev parent reply other threads:[~2013-10-03 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 20:26 [B.A.T.M.A.N.] Alfred batadv-vis json conformance Andrew Lunn
2013-10-02 13:05 ` Simon Wunderlich
2013-10-02 13:36 ` Andrew Lunn
2013-10-06 8:35 ` Nicolás Echániz
2013-10-07 9:00 ` Andrew Lunn
2013-10-02 16:01 ` Antonio Quartulli
2013-10-03 6:09 ` Martin Hundebøll
2013-10-03 8:11 ` Andrew Lunn
2013-10-03 8:22 ` Antonio Quartulli
2013-10-03 8:53 ` Andrew Lunn [this message]
2013-10-03 9:00 ` Antonio Quartulli
2013-10-03 9:05 ` Andrew Lunn
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=20131003085316.GB20056@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=janne.paatero@ruag.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