Hello Colin, I tried to tackle this problem in the branche "bug_fix_multi_upstream_aggregation". I added a unit test suite und I thought the commit "Finished multiupstream membership aggregation" would fix the problem. Unfortunately, as the test suite shows it doesn't.
Class simple_membership_aggregation merges from all downstream the states with include and exclude lists, then filters them with blacklists and whitelists and creates and aggregates the result to multiple upsteams. It is quite complex problem. You could reduce the complexity by writing a class for just one upstream and e.g. interface specific blacklist and white lists. Regards, Sebastian On Wednesday, June 7, 2017 at 10:22:07 AM UTC+2, [email protected] wrote: > > Ok, that explains it. Thanks for the info. > I'd like to get this to work as a firewall rule to block these groups is > not really what I want. I just don't want them forwarded. > > I can dig into the code and post a pull request if I figure it out. > Any pointers on where to start looking ? > > Thanks, > > Colin.. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
