they think they found the issue.

here is their reply:

"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".

The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.

The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."

I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed

Ah, one small mystery solved, for documentational purposes! #RFC6676, "#Multicast Addresses for Documentation": https://datatracker.ietf.org/doc/rfc6676/
(though still not sure why playing with that helps me for ff12::123...)
RFC 6676: Multicast Addresses for Documentation

This document discusses which multicast addresses should be used for documentation purposes and reserves multicast addresses for such use. Some multicast addresses are derived from AS numbers or unicast addresses. This document also explains how these can be used for documentation purposes. This document is not an Internet Standards Track specification; it is published for informational purposes.

IETF Datatracker
Also this datasheet has a field called IP6_MLD_ACT_0_x_x and one called IP6_MLD_ACT_db8_x_x. Acc. to the datasheet to configure forwarding/trapping/copying/dropping settings. The former for #IPv6 #MLD packets with an FF0X::X:X address, and the latter for FF0X::DB8:X:X. And only the latter seems to help with trapping. Even though I'm sending an MLDv1 report for/to ff12::123...
What on earth is this "DB8" about?
#multicast
Also finally found some combination of register setups and diffs for this #Xikestor #Realtek #rtl9300 based chip which correctly traps #MLD packets to the CPU / Linux kernel/bridge, which is necessary to fix #multicast snooping with it.
The combination doesn't fully make sense to me yet though, will need to play around a little more to hopefully get a better understanding. But at least that seems like some progress. Will also need to check #IGMP later.

My initial reflex of that thumbnail of cardboard with the words "no consent = no content" had me think about #multicast:
https://netzpolitik.org/2026/digitale-gewalt-das-lass-ich-mir-nicht-nehmen/

Especially as that's how @dentangle and @onepict have often described multicast.

Digitale Gewalt: Das lass‘ ich mir nicht nehmen

Der Fall von Collien Fernandes schockiert viele. Erschreckend sind allerdings auch die Reaktionen: Menschen verteidigen jetzt ihr vermeintliches Recht, sexualisierte Deepfakes ohne Zustimmung zu erstellen. Und sie offenbaren damit, wie hartnäckig sich alte Machtansprüche halten.

netzpolitik.org
For the #FreeBSD #Google Summer of Code #GSoC 2026 programme, we now have 3 shortlistees for the #EFI MonotonicCounter project, and 1 shortlistee for #multicast snooping in #if_bridge . There is less than 36 hours until the gate closes. Be swift about it!

Visited my parents today and noticed that my father uses #teletext on the TV to get live results for soccer matches. He's not using the internet for that. And I kind of like that idea, teletext is really neat, no pages cluttered with ads, dark mode by default, uniform font, no attention seeking animations.

And that made me wonder if there could be some useful protocols to proxy teletext to IP #multicast, of course :D. (afaik teletext pages are broadcasted round-robin?)

@Selfnet_eV, any ideas?

Using ANSIBLE Automation to configure my Peering Routers

YouTube
Yaiy, iEdon's #dn42 map got support for the #BGP #multicast channel!! You can change the channel via the new button in the top right which initially says "ALL".
https://map.iedon.net/
DN42 Realtime Network Map: The easiest way to visualize the DN42 network

The easiest way to visualize the DN42 network. We retrieve MRT dumps from the DN42 GRC and display ASes, their neighbors, and links on this map.

iEdon-Net

At IETF 125 there will be a meeting to discuss #multicast for AI networks.

They really do want to ruin *everything*

/me cries into terminal