[Olsr-dev] adding config to txtinfo plugin?

Hans-Christoph Steiner (spam-protected)
Thu May 3 22:29:15 CEST 2012

On May 3, 2012, at 2:21 AM, Markus Kittenberger wrote:

> On Thu, May 3, 2012 at 3:28 AM, Hans-Christoph Steiner <(spam-protected)> wrote:
> I have a complete Java wrapper for the txtinfo plugin, but I noticed that the httpinfo plugin provides the configuration while the txtinfo plugin does not.
> afair the txtinfo provides the config already!
> but its (for backward compatibility) not within the /all or default output
> (/all == /neigh/link/route/hna/mid/topo)
> e.g.: wget -t 1 -O -
> (which is infact currently really "all" the txtinfo can provide,..)
> btw you can use 3 letter abbreviations of commands e.g. /int for /interfaces
> and any combinations of commands. e.g. /link/interface/config
> (but btw the output ordering is fixed)
> why I shouldn't add /variables, /interfaces, and /plugins to txtinfo to get all of the info that httpinfo is providing?
> afair it already does exactly this,.. 
> if not add what is missing,..
> Or maybe I should just scrape the httpinfo output...
> not agood idea (especially as current httpinfo will not make into next olsrd versions,..)

So the output of /2hop provides data in a format that is quite difficult to reliably scrape:

IP address	SYM	MPR	MPRS	Will.
	2hop interface adrress	YES	NO	NO	3	YES	YES	NO	7

And it gets worse when there are no 2hop interface addresses:	YES	NO	NO	3	YES	YES	NO	7

Anyone mind if I changed it to output the "2hop interface adrress" data as a comma separated list? Like:

IP address	SYM	MPR	MPRS	Will.		2hop interface adrress list	YES	NO	NO	3,,,

This makes it always have the same number of tab-separated columns, no matter how many "2hop interface addresses" there are.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20120503/924cc316/attachment.html>

More information about the Olsr-dev mailing list