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

[Joe Ayers]

Here's the specifics of what we are doing with broadband-hamnet.org live
example with 0.6.7 :

Hna4
{
                10.161.53.32 255.255.255.248
}

LoadPlugin "olsrd_nameservice.so.0.3"
{
    PlParam "sighup-pid-file" "/var/run/dnsmasq.pid"
    PlParam "interval" "30"
    PlParam "timeout" "300"
    PlParam "name-change-script" "touch /tmp/namechange"
    PlParam "name" "AE6XE-gateway"
    PlParam "10.161.53.36" "AE6XE-voip"
    PlParam "10.161.53.34" "ae6xe-aircam2"
    PlParam "10.85.38.164" "dtdlink.AE6XE-gateway.local.mesh"
    PlParam "service" "http://AE6XE-voip:80/|tcp|10.161.53.36"
    PlParam "service" "http://ae6xe-aircam2:80/|tcp|fishcam-view_view"
}

Subsequently in /var/run/hosts_olsr:

### this /etc/hosts file is overwritten regularly by olsrd
### do not edit

127.0.0.1       localhost
::1             localhost

10.84.38.164    AE6XE-gateway   # myself
10.161.53.36    AE6XE-voip      # myself
10.161.53.34    ae6xe-aircam2   # myself
10.85.38.164    dtdlink.AE6XE-gateway.local.mesh        # myself
10.45.205.112   dtdlink.K5DLQ-UNSM2-100.local.mesh      # 10.44.205.112
10.44.205.112   K5DLQ-UNSM2-100 # 10.44.205.112
172.31.182.82   mid1.K5DLQ-UNSM2-100    # 10.44.205.112 (mid #1)
172.31.182.78   mid2.K5DLQ-UNSM2-100    # 10.44.205.112 (mid #2)
[...]

Regards,
Joe AE6XE

On Sat, Jan 3, 2015 at 2:55 PM, Giuseppe De Marco <(spam-protected)>
wrote:

> 2015-01-03 11:33 GMT+01:00 Conrad Lara <(spam-protected)>:
> > 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.
>
> looking at /var/run/hosts_olsr
>
> (spam-protected):~# cat /var/run/hosts_olsr
> ### this /etc/hosts file is overwritten regularly by olsrd
> ### do not edit
>
> 127.0.0.1 localhost
> ::1 localhost
>
> 172.17.87.3 myhostR # myself
> 172.17.87.39 Bri # 172.17.87.3
> 172.17.87.41 midolini # 172.17.87.3 (mid #1)
> 172.17.87.40 mini # 172.17.87.11 (mid #2)
> [...]
>
> these are the olsr hostnames that we get through olsr.
> We're also looking for a feature, inside nameservice plugin, that
> could announce custom hostnames that are working in every HNA.
> Imagine that we want to resolve an static hostname inside an HNA, a
> server name for example.
> We are looking for a P2P DNS but olsr-nameservice could do that if we
> could insert a static hostname/ip inside olsr nameserver's
> configuration in a way that every olsr node could resolve it in its
> /var/run/hosts_olsr
>
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20150103/6b4a31d2/attachment.html>