[Olsr-users] olsr position update plugin configuration

Wed Nov 28 05:52:48 CET 2012

Hi Ferry,
I would like to thank you for your support.

Thank You.
Bidur

P.S.: By going through the PUD plugin name (Position Update) and reading
the release document (olsrd-0.64/lib/pud/pud.odt), it made me feel that
this plugin will dynamically read the GPS information and update the that
information to the neighbors periodically.

On Tue, Nov 27, 2012 at 6:39 PM, Ferry Huberts <(spam-protected)> wrote:

>
>
> On 27/11/12 12:28, Bidur Devkota wrote:
>
>> Hi Ferry,
>> I am thankful for guiding me to enable the smart gateway. Now I could
>> see the Parameters and Values in the Position tab. Also, I tried to play
>> around with the parameters in the olsrd.conf ( attachment: olsrd.conf),
>> but being a novice user , I think I could not fix it properly.
>>
>> 1. I was not sure whether to load olsrd_sgwdynspeed Plugin or not so I
>> have just loaded it without specifying the speedFile.
>>
>
> no need to load this plugin, unless your internet gateway has a dynamic
> bandwidth.
>
>
>
>> 2. The values shown in Position Tab were all <N/A> so I provided
>> position file by specifying < PlParam "positionFile"
>> "..../Desktop/position" > and could see some values in the Position Tab.
>> (attachments: position, pudPositionTab.png)
>> But the data from this file is updated only at olsrd startup. So how can
>> we get the updated positions periodically.
>>
>
> that is correct. the plugin currently only reads that file during startup.
> the functionality to read it on change is not there. it's not a priority
> for us.
>
> You can always play around with netcat to construct packets with all NMEA
> information/sentences of your position.
>
>
>
>
>> 3. In each machine running the olsr, I could just see the Position Tab
>> where location information about the local machine is shown but I cannot
>> see the location information about the other nodes in the olsr network.
>> (attachment: jsoninfo_Result.txt)
>>
>>
> also correct. the plugin is stateless.
> we do not want to store that information in the plugin since that doesn't
> scale for large networks and embedded routers
>
>
>  Thank You.
>>
>>
>>
>> On Mon, Nov 26, 2012 at 11:25 PM, Ferry Huberts <(spam-protected)
>> <mailto:(spam-protected)>> wrote:
>>
>>
>>
>>     On 26/11/12 16:26, Bidur Devkota wrote:
>>
>>         I went through the documents and attempted to access the pud
>> result.
>>
>>         What I got is: 1. In the command line after running the olsrd , it
>>         says PUD plugin is loaded (screenshot attached:
>>
>>
>>     It's loaded but it's not active since its configuration is invalid
>>     (as is reported, please _read_).
>>
>>     pud is dependent on smart gateway functionality and you have not
>>     enabled that.
>>
>>
>>         pudLoadedTerminal.png) . But in the web interface it says PUD
>> plugin
>>         is not loaded(screenshot attached : pudNotLoaded1.png)
>>
>>         2. I installed the jsoninfo plugin and its output does not show
>> the
>>         position information for PUD plugin. (attachment:
>>         jsoninfo_output.txt)
>>
>>         I have some more confusions: 1. Where/How to configure GPS
>> Daemon. I
>>         am clueless about how the PUD plugin accesses the GPS device
>>         data and
>>         send/receive position updates.
>>
>>
>>
>>     The pud document described what it expects for the GPS information.
>>     How you go about forming those messages or position file is up to you.
>>
>>
>>         Thanks!!
>>
>>
>>         On Fri, Nov 23, 2012 at 6:43 PM, Ferry Huberts
>>         <(spam-protected) <mailto:(spam-protected)>
>>         <mailto:(spam-protected) <mailto:(spam-protected)>>> wrote:
>>
>>
>>
>>         On 23/11/12 12:40, Ferry Huberts wrote:
>>
>>         See the pud architecture document at
>>         http://olsr.org/git?p=olsrd.__**__git;a=blob;f=lib/pud/doc/**
>> pud.____odt;h=____**9f3d31fe0c147c14056437dacc6111**
>> ____ec3889780d;hb=HEAD<http://olsr.org/git?p=olsrd.____git;a=blob;f=lib/pud/doc/pud.____odt;h=____9f3d31fe0c147c14056437dacc6111____ec3889780d;hb=HEAD>
>>
>>         <http://olsr.org/git?p=olsrd._**_git;a=blob;f=lib/pud/doc/pud.**
>> __odt;h=__**9f3d31fe0c147c14056437dacc6111**__ec3889780d;hb=HEAD<http://olsr.org/git?p=olsrd.__git;a=blob;f=lib/pud/doc/pud.__odt;h=__9f3d31fe0c147c14056437dacc6111__ec3889780d;hb=HEAD>
>> >
>>
>>
>>     <http://olsr.org/git?p=olsrd._**_git;a=blob;f=lib/pud/doc/pud.**
>> __odt;h=__**9f3d31fe0c147c14056437dacc6111**__ec3889780d;hb=HEAD<http://olsr.org/git?p=olsrd.__git;a=blob;f=lib/pud/doc/pud.__odt;h=__9f3d31fe0c147c14056437dacc6111__ec3889780d;hb=HEAD>
>>     <http://olsr.org/git?p=olsrd.**git;a=blob;f=lib/pud/doc/pud.**odt;h=*
>> *9f3d31fe0c147c14056437dacc6111**ec3889780d;hb=HEAD<http://olsr.org/git?p=olsrd.git;a=blob;f=lib/pud/doc/pud.odt;h=9f3d31fe0c147c14056437dacc6111ec3889780d;hb=HEAD>
>> >>
>>
>>
>>
>>         raw file:
>>         http://olsr.org/git?p=olsrd.__**__git;a=blob_plain;f=lib/pud/_**
>> ___doc/pud.odt;hb=HEAD<http://olsr.org/git?p=olsrd.____git;a=blob_plain;f=lib/pud/____doc/pud.odt;hb=HEAD>
>>
>>         <http://olsr.org/git?p=olsrd._**_git;a=blob_plain;f=lib/pud/__**
>> doc/pud.odt;hb=HEAD<http://olsr.org/git?p=olsrd.__git;a=blob_plain;f=lib/pud/__doc/pud.odt;hb=HEAD>
>> >
>>
>>
>>     <http://olsr.org/git?p=olsrd._**_git;a=blob_plain;f=lib/pud/__**
>> doc/pud.odt;hb=HEAD<http://olsr.org/git?p=olsrd.__git;a=blob_plain;f=lib/pud/__doc/pud.odt;hb=HEAD>
>>     <http://olsr.org/git?p=olsrd.**git;a=blob_plain;f=lib/pud/**
>> doc/pud.odt;hb=HEAD<http://olsr.org/git?p=olsrd.git;a=blob_plain;f=lib/pud/doc/pud.odt;hb=HEAD>
>> >>
>>
>>
>>
>>
>>
>>         and an example config file (with all parameters documented) at
>>         http://olsr.org/git?p=olsrd.__**__git;a=blob;f=lib/pud/doc/___**
>> _olsrd.conf.default.pud;h=____**7cf142737a89f228afed348d366bcf**
>> ____adb95d5f40;hb=HEAD<http://olsr.org/git?p=olsrd.____git;a=blob;f=lib/pud/doc/____olsrd.conf.default.pud;h=____7cf142737a89f228afed348d366bcf____adb95d5f40;hb=HEAD>
>>
>>         <http://olsr.org/git?p=olsrd._**_git;a=blob;f=lib/pud/doc/__**
>> olsrd.conf.default.pud;h=__**7cf142737a89f228afed348d366bcf**
>> __adb95d5f40;hb=HEAD<http://olsr.org/git?p=olsrd.__git;a=blob;f=lib/pud/doc/__olsrd.conf.default.pud;h=__7cf142737a89f228afed348d366bcf__adb95d5f40;hb=HEAD>
>> >
>>
>>
>>     <http://olsr.org/git?p=olsrd._**_git;a=blob;f=lib/pud/doc/__**
>> olsrd.conf.default.pud;h=__**7cf142737a89f228afed348d366bcf**
>> __adb95d5f40;hb=HEAD<http://olsr.org/git?p=olsrd.__git;a=blob;f=lib/pud/doc/__olsrd.conf.default.pud;h=__7cf142737a89f228afed348d366bcf__adb95d5f40;hb=HEAD>
>>     <http://olsr.org/git?p=olsrd.**git;a=blob;f=lib/pud/doc/**
>> olsrd.conf.default.pud;h=**7cf142737a89f228afed348d366bcf**
>> adb95d5f40;hb=HEAD<http://olsr.org/git?p=olsrd.git;a=blob;f=lib/pud/doc/olsrd.conf.default.pud;h=7cf142737a89f228afed348d366bcfadb95d5f40;hb=HEAD>
>> >>
>>
>>
>>
>>         raw file:
>>         http://olsr.org/git?p=olsrd.__**__git;a=blob_plain;f=lib/pud/_**
>> ___doc/olsrd.conf.default.pud;**hb=____HEAD<http://olsr.org/git?p=olsrd.____git;a=blob_plain;f=lib/pud/____doc/olsrd.conf.default.pud;hb=____HEAD>
>>
>>         <http://olsr.org/git?p=olsrd._**_git;a=blob_plain;f=lib/pud/__**
>> doc/olsrd.conf.default.pud;hb=**__HEAD<http://olsr.org/git?p=olsrd.__git;a=blob_plain;f=lib/pud/__doc/olsrd.conf.default.pud;hb=__HEAD>
>> >
>>
>>
>>     <http://olsr.org/git?p=olsrd._**_git;a=blob_plain;f=lib/pud/__**
>> doc/olsrd.conf.default.pud;hb=**__HEAD<http://olsr.org/git?p=olsrd.__git;a=blob_plain;f=lib/pud/__doc/olsrd.conf.default.pud;hb=__HEAD>
>>     <http://olsr.org/git?p=olsrd.**git;a=blob_plain;f=lib/pud/**
>> doc/olsrd.conf.default.pud;hb=**HEAD<http://olsr.org/git?p=olsrd.git;a=blob_plain;f=lib/pud/doc/olsrd.conf.default.pud;hb=HEAD>
>> >>
>>
>>
>>
>>
>>
>>         If you enable the httpinfo plugin as well, then you get a tab with
>>         the pud position. I think the data is also available by means of
>> the
>>         jsoninfo plugin but I've never used that.
>>
>>         If after reading these you still have questions, mail again
>>
>>         On 23/11/12 12:22, Bidur Devkota wrote:
>>
>>         Hi All,
>>
>>         I was searching for ways to share the position between the nodes
>> in
>>         OLSR network. Luckly, I got to know about pud plugin for OLSR. I
>>         tried to install  it and access the data. Like for dot_draw and
>>         txtInfo plugin, we can see the plugin result by monitoring in the
>>         assigned port number (in /etc/olsr.conf) . For example
>>         127.0.0.1:2006 <http://127.0.0.1:2006> <http://127.0.0.1:2006>
>>         <http://127.0.0.1:2006>. I am
>>
>>         hoping that there should be some similar ways to see the pud
>> plugin
>>         data as well. But I did not find any luck. Even searching the web
>>         could not link me to some examples showing the way to configure
>> and
>>         access pud plugin. Are there any special configuration required
>> for
>>         pud? It would be of great helo if I can get through some exaples
>> for
>>         it.
>>
>>         Thanks !
>>
>>         Bidur
>>
>>
>>
>>
>>         -- Ferry Huberts
>>
>>
>>
>>
>>         -- Regards, Bidur Devkota
>>
>>
>>
>>
>>
>>     --
>>     Ferry Huberts
>>
>>
>>
>>
>> --
>> Regards,
>> Bidur Devkota
>> Asian Institute of Technology, Thailand
>>
>>
>>
>>
> --
> Ferry Huberts
>

-- 
Regards,
Bidur Devkota
Asian Institute of Technology, Thailand
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20121128/838bcad8/attachment.html>