Yaiy, it works! The full integration test for a #multicast audio stream at #Freifunk involving #Gluon, #batman_adv, @gstreamer and #brmldproxy + #pim6sd + #EmbeddedRP with routing between @ffhl and a test domain at @Freifunk Vogtland was successful (at least with pim6sd in #MLDv1 mode).

Next need to do a few, small updates to my brmldproxy integration pull-requests for Gluon. And need to look into the #MLDv2 mode issues with #pim6sd. And need to document some more stuff.

I trying to add #mldv2 ( #ipv6 #multicast ) support into #lwip
According RFC It looks that subscribers should always send report to query from router but I tried this with both Win and Linux an no OS is doing it.

Did I get it wrong?
current lwip with mldv1 seems to be ignoring any queries as well.

More details here: https://networkengineering.stackexchange.com/questions/84037/should-ipv6-multicast-subscribers-send-report-to-query

@dentangle ah, yes, #MLD queries should kind of work around this issue. As long as the lcsync server does not lose an MLD querier election to another MLD querier.
I'm wondering if it would be feasible and help to write an #RFC to update MLDv1 which disallows report suppression. At least in theory such a small update would maybe be faster to propagate. Faster than demanding that everyone fully abandons #MLDv1 and migrates to #MLDv2.
#IETF #multicast