[Olsr-dev] Integration of multicast plugins

[Teco Boot]

The main diff between BMF and the mdns->p2pd->dnssd lineage is the encap method. BMF has its own packet distribution, where the others use OLSR messages. p2pd is the improved mdns (bug fixing, code cleanup and configuration for non-mdns traffic. dnssd is the improved p2pd. Meanwhile, mdns is enhanced for support of multi-connected links.

All plugins flood, they do not set up a multicast group specific distribution tree (dense mode without pruning).

I support the suggested merge. First step would be single plugin for the mdns->p2pd->dnssd lineage, could be a next version mdns (aka olsrd_mdns.so.1.1.0). Question: "if no filter, then use the  PlParam "UdpDestPort" "224.0.0.251 5353" parameter as default? Only the 5353 port filter?

Concerns: IPv6 and variants for duplicate filtering. And MPR. I tested BMF on some phones recently and experienced some problems. Probably related to MPR. The Thales version where BMF was developed had an improved MPR selection, that worked well with their link cost probe.

Teco 

Op 2 apr. 2013, om 08:29 heeft Henning Rogge <(spam-protected)> het volgende geschreven:

> On 04/01/2013 10:47 PM, Dan Staples wrote:
>> Some weeks ago I emailed the list about a plugin I put together (dnssd),
>> which was built on top of the p2pd plugin. In response, several people
>> expressed a desire to have all of the multicast plugins consolidated
>> into one, instead of accepting a new plugin. I wanted to check in again
>> to see what that consolidated plugin might look like.
>> 
>> It seems like there are two main sources for multicast forwarding in
>> olsrd: the bmf plugin, and the mdns->p2pd->dnssd lineage of plugins.
> 
> I don't think this is correct.
> 
> mdns is (or was?) a simplified copy of bmf, both are using "dense mode multicast", similar to the SMF protocol.
> 
> p2pd (and maybe dnssd?) are using "sparse mode multicast" according to my knowledge.
> 
>> Is
>> there any preference for either one? Are there any features of these
>> that should or should not be included? The features I added in the dnssd
>> plugin are only applicable to someone using Avahi, and so those could be
>> optionally turned on or off depending on the plugin configuration, if it
>> is decided to go with mdns/p2pd/dnssd.
>> 
>> Also, would it be a requirement to not use any external libraries, to
>> make it as portable as possible?
> 
> Not sure multicast plugins are portable anyways, because the kernel interface to do multicast is very OS specifc.
> 
> Henning Rogge
> 
> 
> -- 
> Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> Kommunikationssysteme (KOM)
> Fraunhofer Straße 20, 53343 Wachtberg, Germany
> Telefon +49 228 9435-961,   Fax +49 228 9435 685
> mailto:(spam-protected) http://www.fkie.fraunhofer.de
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev