An initial #PIM #multicast peering was added to the #Nobreakspace / @chaotikumev on #dn42. The #BGP multicast channel approach works great. And receiving an audio stream from three hops away on an ethernet port in the hackspace worked like charm. Only receiving it on the hackspace WiFi with default #OpenWrt settings was really choppy. It's not yet as optimized for that as it is on our #Freifunk Wifi at @ffhl ;-).
Audio test streams at @ffhl were now duplicated from their #IPv6 GUA (global unique addresses) to ULA (unique local addr.), for #dn42 compatibility. Not quite happy about duplicating, as it kind of defeats the purpose of #mulitcast, but getting GUAs in #dn42 accepted would probably be a difficult task. Has anyone NAT'd IPv6 mc before :D?
Next up will be to set up a #PIM multicast peering between @chaotikumev / #Nbsp and @ffhl. Getting #Freifunk and #dn42 multicast connected could be interesting.
@ffhl or more precisely the embedded RP #multicast destinations derived from the IPv6 GUA unicast prefixes were copied to embedded RP ones from the ULA.
Also two SSM (source-specific multicasr) copies were added, one with a GUA source address and the other with an ULA source one. SSM won't be fully usable in our #Freifunk network yet, though (but it should work on #dn42).
The #PIM + #BGP configs at the @chaotikumev / #Nbsp are also currently "documented" / dumped to this page: https://wiki.chaotikum.org/infrastruktur:host:dobby-setup. And will likely get a bit more tweaking until the #39c3. Later needs to be copied to the #dn42 wiki.
I had also hacked together a watchdog script which disables route imports+exports on the BGP #multicast channel in bird if a BGP neighbor does not also run a PIM daemon. This is to work around this issue which I mentioned a few days ago: https://wiki.dn42.dev/howto/pim-multicast-vs-unicast-issue
infrastruktur:host:dobby-setup [Chaotikum e.V.]