Re: [B.A.T.M.A.N.] Alfred batadv-vis json conformance

[Antonio Quartulli <antonio@meshcoding.com>]

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

On Thu, Oct 03, 2013 at 10:53:16AM +0200, Andrew Lunn wrote:
> > > 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. 

Oh ok, I didn't think about this case.

> 
> > What about the source version? How did you get it from the module?
> 
> It is the alfred version, not the kernel module version.
> 

Ok (but I don't see how it can be useful)


Thanks!


-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]