[Olsr-dev] PlParam "IP.ADDR" "another-name.mesh"

[Conrad Lara]

Is this a Commotion only change that it doesn't accept it? or something that just recently was pulled out?  Quick glancing the code it looks like it still should work to me.

I am using this feature on my network (0.6.7) from OLSR.org with BBHN patch sets that don't touch nameservice) without issue.

This is the exception to the normal rule of having a setting name value pair in that it uses the IP address is where the parameter name normally is and the value is the hostname.

Make sure you are using a properly formatted IP address. Also the IP used has to be in your local list of OLSR listens addresses OR your HNA announcement range otherwise it will be thrown out as invalid.

Sent from my iPhone

> On Jan 3, 2015, at 1:24 AM, Ferry Huberts <(spam-protected)> wrote:
> 
> 
> 
>> On 02/01/15 16:50, Giuseppe De Marco wrote:
>> Hi all,
>> 
>> last night I saw that the parameter
>> 
>> PlParam "10.87.x.y" "another-hostname.mesh"
> 
> 
> There is no such parameter, see https://github.com/opentechinstitute/olsrd/blob/commotion/lib/nameservice/src/nameservice.c#L256
> 
> The format is
> 
> PlParam "<.name>" "<value>"
> 
> So for example
> 
> PlParam "suffix" "mysuffix"
> 
> 
>> 
>> doesn't work.
>> Reading the
>> 
>> https://github.com/opentechinstitute/olsrd/blob/commotion/lib/nameservice/src/nameservice.c
>> 
>> in line 227 and then in line 435 I saw that this parameter were not
>> parsed at all.
>> Is there any possibility to have this feature fully working in the
>> next months or should we - in my local mesh community- develop it by
>> hand ?
>> 
>> If we have to implement this by hand could someone describe us some
>> hints and suggestions about the code design to speed up the
>> integration of theese little bunch of code ?
>> 
>> Thank you all,
>> olsrd is awesome,
>> Giuseppe
> 
> -- 
> Ferry Huberts
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev