1 Dec
2016
1 Dec
'16
1:11 p.m.
I agree with Gio, we also tried to use mDNS/avahi in several projects
and it was always a fail, in addition the layer2 dependency is a
restrictions which reduces the possible impact of the services sharing.
An alternative option would be to use the bmx6 SMS plugin [1], which
allows the transfer of small files using the routing packets. Here an
example of usage [2] and the code [3].
Using ALFRED from batman-adv would be also an option. On LiMe we are
already using it for the dhcp leases share system of dnsmasq, but again
it would work only for the cloud (not the entire network). So a kind of
bridge might be implemented.
Would be nice to put some effort here.
Cheers.
[1] https://github.com/axn/bmx6#sms-plugin
[2] http://bmx6.net/projects/bmx6/wiki/Mdns
[3] https://github.com/routek/qMp/tree/testing/packages/bmx6-mdns
On 01/12/16 12:51, Gio wrote:
In ninux.org we historically tried to take advantage
on mDNS/avahi lot of
times, it is a mess and in the end all the time we decided it was too buggy
and bloaty to make use of it...
With time i can look for more info and arguments agains mDNS to forward but
right now i am very busy!
Cheers!!
On Sunday 27 November 2016 09:08:52 nicopace wrote:
--
./p4u
Hi All,
My name is Nicolás, I'm from Argentina and I'm working promoting
community networks while I travel in Latin America... Glad to be part
of this community, and thanks to you all for all you have been doing so
far, it is amazing!!!
I wanted to share with you some of my last work (that I've been
discussing with Nico Echaniz, who suggested to migrate it to here),
about how we can promote the use of local services.
My view about this has been on using local discovery techniques to
identify which local services are around using mdns, and then promote
those services via a captive portal.
There are many services that are already shared in this way (like
printers, media repositories, chat apps) and it is quite easy to add
new ones or index those that are not added manually also.
I have also defined a strategy on how to deploy this on LiMe based on
Nico`s experience on multicast packages (those used by the mDNS
discovery mechanism) on mesh networks (quite a mess for now)... so I
found a workaround for this specific case.
We cound add a daemon to LiMe that permanently scans its local network
searching for services, and shares that information via Alfred.
Together with another daemon that listens to Alfred and adds that
information to the LiMe mDNS Service (Avahi)... that sorts out the
multicast issue and lets us share that valuable information efficiently.
For those services that don't support mDNS we could add an interface on
luci to manually administer them.
Finally, we could add a section on the Captive Portal to show this
information.
What do you think?
Regards,
--
Nicolás Pace
http://www.linkedin.com/in/nickar
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev