@T_X #lcsync sends MLD Queries, so hopefully that will stop any #RFC4541 switches from getting confused. MLDv1 makes a real mess of this - be nice to get rid of it. The very idea of a switch trying to guess what is a router is madness, when the simple answer in IPV6+MLD2 terms is does this port listen to ff02::16 ?

@T_X In client mode #lcsync leaves it to the OS, but in server mode it listens to MLD traffic so it knows when to send something, and what. #RFC4541 doesn't apply here, as lcsync is not acting as a switch (lcsync is not switching traffic, but is a source or a sink). This is a prelude to every node becoming a potential multicast router, but that's for another milestone 😉

@dentangle interesting, why is #lcsync listening on #MLD itself, instead of leaving this fully with the OS?
Is the implementation taking #RFC4541 into consideration? Specifically the part where it says that snooping switches may only forward reports to ports with multicast routers.