pali

Well, I have not looked at it deeply how to implement it. If you this it is simple, feel free to open a pull request.

> Oh and maybe have MAX_IF be configurable. igmpproxy is often run on memory restrained systems `struct IfDesc` is 50-60 bytes long. You would have to about 100 000 interfaces...

Could you please post patches in normal way, via git repository and pull request, and not in zip files which github cannot process?

Well, could you please really post patches in preferred way via git pull request? This is really hard for me review patches in this way. And also now if you...

Patches for updating documentation are welcome.

Could you please describe problem/error more deeply? After quick look I do not see what is the problem.

Yes! I understood what you mean and how your change fixes (or rather workarounds?) this problem. I wrote about this issue also in comment: https://github.com/pali/igmpproxy/pull/32#issuecomment-620887757

Hello! Could you describe why is this change needed? Is it fixing some bug or are there any issues with current implementation?

Ok. Now I see the reason. Anyway, I'm not sure if it is safe to "upgrade" all packets unconditionally. RFC documents are strict how client should behave but because I...

Ok, please look at this how hard is to add config option and if you can do it during your IGMPv3 support on downstream interfaces.