Post AaB0K8rfxt6HvjCvy4 by T_X@chaos.social
 (DIR) More posts by T_X@chaos.social
 (DIR) Post #AaB0K7u7XJSgx1LN8i by T_X@chaos.social
       2023-09-20T23:26:16Z
       
       0 likes, 0 repeats
       
       Nice, the "#Bridge #MLD #Proxy" daemon (#brmldproxy) I stitched together with TC (#TrafficControl) generally seems work on a #Freifunk #Gluon #mesh node. In this context it is supposed to make IPv6 #multicast routers/-ing work again. Currently Gluon filters all MLD to reduce layer 2 overhead with #batman_adv With brmldproxy it can be configured to only emit MLD reports for routable multicast addresses.Next steps: Creating init scripts + packages. Maybe adding hotplugging support to brmldproxy
       
 (DIR) Post #AaB0K8rfxt6HvjCvy4 by T_X@chaos.social
       2023-09-20T23:41:16Z
       
       0 likes, 1 repeats
       
       And then the next steps for admins would be to either set up #lcroute from @librecast or #pim6sd, which is maintained by @troglobit, on #Freifunk gateways. To interconnect #Freifunk domains and communities, to make #multicast services reachable between them. Then your domain for multicast would increase from maybe 300 Gluon nodes / 600 client devices average to potentially >40k Gluon nodes / >80k client devices. Hopefully getting things closer to a critical mass.#decentralization