Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#2 Restrict igmp reports forwarding to upstream interface

closed-fixed
nobody
None
5
2010-02-23
2009-12-11
Stefan Becker
No

I have an UPnP server on the internal network, i.e. it sends out multicast messages for SSDP (239.255.255.250). igmpproxy forwards them to the upstream interface. If I use the new "whitelist" keyword on the downstream interface then this doesn't happen, but that means that the UPnP server won't be visible on the other downstream interfaces.

The attached patch utilizes the "whitelist" keyword also on the upstream interface. I wasn't sure how to implement this correctly. I choose the solution of blocking upstream Join/Leave messages for non-whitelisted multicast groups. It seems to work OK in my setup.

If this patch is OK for you I can try a "git push" as I have a SF account and should(?) have git write access.

commit 9c7fedd9d4692bcf1404d5f831d05e7090164d39
Date: Fri Dec 11 21:08:57 2009 +0200

Restrict igmp reports forwarding to upstream interface

Utilize the new "whitelist" keyword also on the upstream interface definition.
If specified then only whitelisted multicast groups will be forwarded upstream.

This can be used to avoid publishing private multicast groups to the world,
e.g. SSDP from a UPnP server on the internal network.

Discussion

  • Committed.

    P.S.: It's better to format a patch using command 'git format-patch HEAD^' and post resulting file here or send it via email.

     
    • status: open --> closed-fixed