igmp proxy open source comparison

[Michael Smith]

Hello,
First, thanks for creating/supporting an open source igmp proxy implementation for Linux.

Can you tell me how your implementation compares to http://sourceforge.net/projects/igmpproxy/ ? I've noticed a few obvious things - your implementation is more recent, is written in C++ instead of C, doesn't support non-Linux or Linux <= 2.6.32. I believe neither support IGMPv3 (but do support v2). I'm trying to determine what is the best open source implementation to use with my product. My goal would be to avoid having to make a lot of changes to the version I use. How would you rate your software in terms of completeness and bugfreeness? Let me know if you can recommend your implementation or others I may not be familiar with.

Thanks for your time,

Mike

[Sebastian Wölke]

Hello Mike,

thank you for your interests. Here is a summary of the pros and cons of both implementations.

Because the mcproxy is written in c++, it needs more main memory and so it is less suitable then the igmpproxy for low power embedded system.

There are no known bug in both implementation, but igmpproxy is much older and because of that the more used implementation. It is probably more bugfree than mcproxy.

Mcproxy supports the group management protocols IGMPv2 and MLDv1, this mean it handles IPv4 and IPv6 multicast, while igmpproxy handles only IPv4 multicast. In the near future the mcproxy will be updated to support IGMPv3 and MLDv2.

The mcproxy supports multiple multicast routing tables, this mean you can run more than one multicast proxies on the same machine. Igmpproxy doesn't support this feature.

Igmpproxy and mcproxy are only management software for the multicast routing tables of the Linux kernel, the throughput depends only on the Linux kernel and the machine itself.

If you have further comments or question don't hesitate to connect me.

Best regards,

Sebastian

[Sebastian Wölke]

Hello Mike,

thank you for your interests. Here is a summary of the pros and cons
of both implementations.

Because the mcproxy is written in c++, it needs more main memory and
so it is less suitable then the igmpproxy for low power embedded
system.
There are no known bug in both implementation, but igmpproxy is much
older and because of that the more used implementation. It is probably
more bugfree than mcproxy.
Mcproxy supports the group management protocols IGMPv2 and MLDv1, this
mean it handles IPv4 and IPv6 multicast, while igmpproxy handles only
IPv4 multicast. In the near future the mcproxy will be updated to
support IGMPv3 and MLDv2.
The mcproxy supports multiple multicast routing tables, this mean you
can run more than one multicast proxies on the same machine. Igmpproxy
doesn't support this feature.
Igmpproxy and mcproxy are only management software for the multicast
routing tables of the Linux kernel, the throughput depends only on the
Linux kernel and the machine itself.

If you have further comments or questions don't hesitate to connect me.

Best regards,
Sebastian

2013/5/2 Michael Smith <msmit...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups
> "Multicast Proxy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to multicast-pro...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Michael Smith]