[OLSR-users] Re: Topology Question

[Lorenz Schori]

hi

take a look at txtinfo-module which is used by freifunk. it is a  
stripped down and cleaned up version of httpinfo. if you just enclose  
the plaintext stuff into xml tags you're done.

i'm not sure if this module was included into the olsr-cvs branch. in  
freifunk it is included as a patch.

btw. i tought about implementing json as an output option into  
txtinfo. for dynamic web-applications i like it much better than the  
xml stuff.

because you're mentioning googlemaps. i've put together an olsr- 
plugin which floods the locations information thru the mesh. it can  
read the position information either from the olsrd.conf or from a  
specified file, which can be updated by other means (like gpsd).
olsr-location has the same outputformat like txtinfo. again, json  
probably fits better...

txtinfo plugin:
http://ff-firmware.cvs.sourceforge.net/*checkout*/ff-firmware/ff- 
devel/olsrd-txtinfo.patch

olsr-location plugin:
http://znerol.ch/files/olsr-location-0.1.tar.gz

cheers
lorenz

Am 02.03.2007 um 14:43 schrieb Michael Oh:

> Simon -
>
> If you do the xslt/google mashups code, I think I could handle
> converting the dot-draw plugin to provide xml also...
>
> Michael Oh
>
> On 3/2/07, Simon Knight <(spam-protected)> wrote:
>> Anyone savvy enough to write a plugin to export (similar to the dot
>> draw plugin) in XML format?
>> This would be great to XSLT with some nice google maps mashups.
>>
>> Cheers
>> Simon
>>
>>
>> On 2/16/07, Aaron Kaplan <(spam-protected)> wrote:
>> >
>> > hi Soumedra,
>> >
>> >    the link below is an adaptation of the olsr dot_draw plugin. We
>> > just simply colored the links according to ETX values.
>> >
>> > About maintaining the network: well, each participant in the mesh
>> > maintains it for him/herself. Once the mesh reaches a certain
>> > density / size, it will almost always find different routes in case
>> > one node is not maintained properly (i.e. crashes or so)
>> >
>> > best regards,
>> > a.
>> >
>> > On Feb 13, 2007, at 5:58 PM, Soumendra Nanda wrote:
>> >
>> > > Hi
>> > >
>> > > http://sandwich.funkfeuer.at/topo/
>> > >
>> > > How did you guys generate that above map?
>> > >
>> > > Thats a pretty big OLSR setup.
>> > >
>> > > How do you guys monitor and manage that network? Do you just  
>> rely on
>> > > manual monitoring and calling up people on the phone or via a  
>> message
>> > > board or email?
>> > >
>> > > Thanks
>> > > Soumendra
>> > >
>> > >
>> > >
>> > >
>> > >>
>> > >> Message: 6
>> > >> Date: Tue, 13 Feb 2007 10:41:53 +0100
>> > >> From: Bernd Petrovitsch <(spam-protected)>
>> > >> Subject: Re: [OLSR-users] Topology question
>> > >> To: OLSR discussion and development <(spam-protected)>
>> > >> Message-ID: <(spam-protected)>
>> > >> Content-Type: text/plain
>> > >>
>> > >> On Mon, 2007-02-12 at 16:48 -0500, Soumendra Nanda wrote:
>> > >> [...]
>> > >> > This may sound like a real newbie question but is the the  
>> topology
>> > >>
>> > >> Who cares;-)
>> > >>
>> > >> > returned by the OLSR topology plugin the full link state
>> > >> topology with
>> > >> > all links and all nodes listed
>> > >> > OR
>> > >> > a partial  link state topology: ie a subset of links and a  
>> list
>> > >> of all
>> > >> > known reachable nodes
>> > >>
>> > >> It is all the one daemon you asked knows about the topology net.
>> > >> This maybe the whole net or only a part of it (and the daemon  
>> cannot
>> > >> tell you because he doesn't know).
>> > >>
>> > >> > Is there an option to tune the topology detail in olsr-0.  
>> 4.10?
>> > >>
>> > >> No. This is mainly because it generates output for graphviz'  
>> `dot`
>> > >> program and that program doesn't support subgraphs (though  
>> the dot
>> > >> file
>> > >> syntax supports it).
>> > >>
>> > >> If you know another - better - graph visualization tool (which
>> > >> runs at
>> > >> least/also on Unix/Linux), we all are happy to get a plugin for
>> > >> it. The
>> > >> topology map of the FunkfFeuer net - http:// 
>> sandwich.funkfeuer.at/
>> > >> topo/
>> > >> - is also pretty messy nowadays.
>> > >>
>> > >>         Bernd
>> > >> --
>> > >> Firmix Software GmbH                   http://www.firmix.at/
>> > >> mobil: +43 664 4416156                 fax: +43 1 7890849-55
>> > >>           Embedded Linux Development and Services
>> > >>
>> > >>
>> > >>
>> > >>
>> > >
>> > > _______________________________________________
>> > > olsr-users mailing list
>> > > (spam-protected)
>> > > https://www.olsr.org/mailman/listinfo/olsr-users
>> > >
>> >
>> >
>> > _______________________________________________
>> > olsr-users mailing list
>> > (spam-protected)
>> > https://www.olsr.org/mailman/listinfo/olsr-users
>> >
>>
>> _______________________________________________
>> olsr-users mailing list
>> (spam-protected)
>> https://www.olsr.org/mailman/listinfo/olsr-users
>>
>
>
> -- 
>
> Thanks!
> Michael Oh
>
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: Signierter Teil der Nachricht
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20070302/eb316fca/attachment.sig>