> I am pleased to announce the public release of pimbd, the PIM > implementation that was demonstrated during the last Bits and Bites in > Prague.
I've now looked at it, and it's looking good to me. It's roughly the size of babeld (10kloc), the code looks reasonably clean, and there appears to be dome amount of OpenWRT integration. I've been able to compile it under Debian (libubox, grumble grumble), I've been able to get it to join IPv6 multicast groups, but I've been unable to get it to actually route multicast. Probably something wrong on my side, I'll wait until it migrates into OpenWRT A few questions. Does SSMBIDIR interoperate with plain BIDIR? What happens when there are both BIDIR and SSMBIDIR routers in the Homenet? Could you please explain what problem you're solving with the SSMBIDIR extension? I'm not a multicast specialist, so please correct me if I'm wrong, but I understand that BIDIR: (1) doesn't optimise SSM trees; (2) wants a well-defined default route. Which problem exactly are you trying to solve with SSMBIDIR? Both? If just (1), might we as well go with plain BIDIR? What problem does the proxying business attempt to solve? And what does it use TCP for? To compile this under Debian: apt-get install liblua5.1-0-dev git clone http://git.openwrt.org/project/libubox.git (cd libubox && make && sudo make install) sudo ldconfig /usr/local/lib git clone https://github.com/Oryon/pimbd (cd pimbd && make && sudo make install) Careful, libubox compilation fails silently if liblua is not version 5.1. -- Juliusz _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
