RE : [lwip-devel] igmp implementation

[Goldschmidt Simon]

> But you don't talk about the "big" problem (not so big, but): the
ip_input patch: even with a "per netif" group list, the
> current ip_input code only select one netif to do the processing. If
two netif "join" the same group, what do you propose to
> handle that? I think it could be more intrusive (in the source code
and in execution time). This point if the most important
> to my point of view. A better IGMP implementation will also support
SO_REUSEADDR/PORT (see https://savannah.nongnu.org/task/?
> 6995 <https://savannah.nongnu.org/task/?6995> ), since two
sockets/services could need to receive the same information. Last,
> a socket level filter will be the last step (because, when a socket do
a "leavegroup, there can be already packets in its
> recvmbox from this group, and they should be dropped, and not given to
the application).

That's a thing we have to change some time. But the code should stay the
same size if someone (like me) doesn't really need igmp/reuseaddr/port!
         
> There is also some tips to change in igmp.c : it should better use
memp than mem

I certainly agree on that! :-)