Fosstodon

T_XYaiy, das hat gefetzt und geklappt! Beim inlineskaten auf dem nach Hause Weg live und entspannt dem <a href="https://chaos.social/@schenklradio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@schenklradio</a> über einen mobilen <a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freifunk</a> Router und per <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> zugehört :D. Die eigene Basteltechnik hat geklappt. Nächstes mal muss ich aber früher einschalten, hab leider nur die letzten 30min. mitbekommen. Danke <a href="https://chaos.social/@schenklradio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@schenklradio</a>!

T_XI have to say, I'm getting more comfortable with <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> services. And I find it fascinating how with its templates and powerful dependency feature I could achieve some wild, very dynamic stacking of <a href="https://floss.social/@gstreamer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gstreamer</a>, <a href="https://fosstodon.org/@pipewire" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pipewire</a>, <a href="https://chaos.social/tags/mpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mpd</a>, <a href="https://chaos.social/tags/mpv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mpv</a> and <a href="https://chaos.social/tags/SAP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SAP</a> / <a href="https://chaos.social/tags/RFC2974" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC2974</a> with only a few lines for various systemd services. So for instance a <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> SAP announcement of <a href="https://chaos.social/@schenklradio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@schenklradio</a> will only appear if something plays on that pipewire device, which only happens if that radio is on air and reachable.

T_XSo, <a href="https://chaos.social/@schenklradio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@schenklradio</a> wäre jetzt testweise auch mal im <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> per <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> mit <a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@videolan</a> verfügbar. <a href="https://chaos.social/@tokudan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tokudan</a>: vll. könnte das ja eine kleine Motivation sein, um mal multicast routing zwischen <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> und <a href="https://chaos.social/@FreifunkHamburg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@FreifunkHamburg</a> einzurichten :-)?

Brett Sheffield (he/him)Remember, when a tree falls in a <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> forest, and no one is listening, no data is sent.

T_XWas hier in Lübeck mit <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> auch geht: Am Strand das einzig wahre <a href="https://chaos.social/tags/vibe_coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vibe_coding</a>, mit Mate, Musik per <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> aus dem <a href="https://chaos.social/tags/MeshNetzwerk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MeshNetzwerk</a> vom mobilen LTE <a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freifunk</a> Knoten mit <a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@videolan</a> hören und per <a href="https://chaos.social/tags/MPD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MPD</a> für alle moderieren :D.Die Bilder wurden bequem und lokal fix ohne Volumenbelastung via <a href="https://chaos.social/tags/Syncthing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Syncthing</a> vom Handy auf den Laptop kopiert, auch dank der <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> basierten <a href="https://chaos.social/tags/LocalPeerDiscovery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LocalPeerDiscovery</a> von Syncthing, die hier bei uns im <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> geht.

T_X<a href="https://norden.social/@jpl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jpl</a> <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> <a href="https://social.freifunk.net/@batadv" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@batadv</a> <a href="https://vogtland.social/@Freifunk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Freifunk</a> bin gerade noch dabei, den <a href="https://chaos.social/tags/rtl83xx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rtl83xx</a> basierten Switch, den <a href="https://chaos.social/@bdobe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bdobe</a> empfohlen hatte, ein bisschen was am IGMP/MLD snooping im Linux kernel zu fixen und habe unseren <a href="https://chaos.social/tags/Nobreakspace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nobreakspace</a> wieder ans <a href="https://chaos.social/tags/dn42" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dn42</a> angeschlossen, will danach dann auch das layer 3 <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> routing noch zwischen <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> und unseren hackspace einrichten. Danach wäre der Plan, das über <a href="https://chaos.social/tags/dn42" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dn42</a> und das <a href="https://chaos.social/tags/ICVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ICVPN</a> zu machen, genau. Wer aber direkt schon layer 3 multicast peeren möchte, gerne bescheid sagen :-).

T_X<a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> <a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@videolan</a> die technische Hintergrund der neuen Streams: Statt <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> / UDP / <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RTP</a> / <a href="https://chaos.social/tags/Opus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Opus</a>. Ist es jetzt: IPv6 / UDP / <a href="https://chaos.social/tags/MPEG2TS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MPEG2TS</a> / RTP / Opus. Es ist also noch ein gaaanz toller (Sarkasmus), proprietärer, unnötiger Protokollheader dazwischen gekommen, der nur das Paket aufbläht. VLC v3 kann aber noch nicht das <a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> <a href="https://chaos.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> standardisierte, native RTP-Opus, das kann erst der nightly/v4. Sobald VLC endlich mal releasen sollte, schmeiß ich das MPEG-TS auch ganz schnell wieder weg.<a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a>

T_XDie <a href="https://chaos.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a> streams im <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> sind jetzt zusätzlich auch mit dem <a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@videolan</a> v3 unter "Local Netzwork -> Network streams (SAP)" find- und abspielbar. Nur die mit "(v4)" markierten brauchen noch den <a href="https://chaos.social/tags/VLC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLC</a> v4/nightly. Den v4 nightly zum Laufen zu bekommen, schien bei vielen noch eine zu große Hürde zu sein. Würde mich sehr über Feedback freuen, ob es jetzt auch bei anderen geht im <a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ffhl</a> geht.

T_X<a href="https://social.ffmuc.net/@freifunkMUC" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@freifunkMUC</a> ansonsten fände ich es auch noch sehr spannend, wenn man als weiteren Service für VPN und die VMs auch <a href="https://chaos.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a> dann anbieten könnte. Auch per <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> und <a href="https://chaos.social/tags/PIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PIM</a> / <a href="https://chaos.social/tags/pim6sd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pim6sd</a> über das <a href="https://chaos.social/tags/IntercityVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IntercityVPN</a> zwischen Communities dann irgendwann. Das gäbe es meines Wissens nach auch bei keinem kommerziellen Angebot bisher. Aber dann müssten wir nochmal schauen, wie man das gerade mit euren <a href="https://chaos.social/tags/GluonParker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GluonParker</a> Bestrebungen noch hinbekommen könnte.

Brett Sheffield (he/him)With Alonso's "help", I merged in restricted channel support to <a href="https://chaos.social/@librecast" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@librecast</a> today.This lets a receiver set a filter on an inbound <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> channel with a keyring and capabilities.Any traffic arriving must be cryptographically signed and have a token signed by a key on the filter keyring, and have the required capability bits set, otherwise it is silently dropped by standard API recv calls like lc_channel_recvmsg().<a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librecast</a>

Nessbethyeah. :-/ Latest iOS simulators somehow can not use multicast anymore. Working fine on real device ¯\_(ツ)_/¯ `nw_browser_fail_on_dns_error_locked [B1] nw_browser_dns_service_browse_callback failed: PolicyDenied(-65570)`<a href="https://social.bitwig.community/tags/ios" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ios</a> <a href="https://social.bitwig.community/tags/xcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xcode</a> <a href="https://social.bitwig.community/tags/simulator" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#simulator</a> <a href="https://social.bitwig.community/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> <a href="https://social.bitwig.community/tags/bonjour" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bonjour</a>

Brett Sheffield (he/him)<a href="https://chaos.social/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> RFC 9777 was released last month, replacing RFC 3810 for <a href="https://chaos.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a> Listener Discovery ( <a href="https://chaos.social/tags/MLD2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MLD2</a> ).Reviewing this, aside from a bunch of textual clarifications and fixes, the only real technical change to speak of was an adjustment to the Multicast Address Listening Interval (MALI).I've patched <a href="https://chaos.social/tags/libmld" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libmld</a> and <a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librecast</a> with the new timer value and the change will be included in the next release.<a href="https://datatracker.ietf.org/doc/html/rfc9777" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://datatracker.ietf.org/doc/html/rfc9777</a>

T_XCurse you, <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> bridge (or <a href="https://chaos.social/tags/DSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DSA</a> or <a href="https://chaos.social/tags/switchdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switchdev</a>) - why do you send this uncalled-for <a href="https://chaos.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> deletion notification... (and do I dig deeper into this, maybe finding a bug?, or should I just go for the other approach I wanted to implement anyway, which wouldn't need to hook into the VLAN notifications in the first place...)<a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> <a href="https://chaos.social/tags/rtl83xx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rtl83xx</a> <a href="https://chaos.social/tags/switch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switch</a>

T_XSo, one more switch arrived, the GS1900-24E, the non-<a href="https://chaos.social/tags/PoE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PoE</a> variant of the <a href="https://chaos.social/tags/ZyXEL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ZyXEL</a> switch that I got before. And without PoE it was even about half the price on <a href="https://chaos.social/tags/Kleinanzeigen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kleinanzeigen</a>, just 35€. I wanted to have one that I could install at our hackspace, the <a href="https://chaos.social/tags/Nobreakspace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nobreakspace</a>, for production and one for development on <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a>. This also means that things are getting more serious now, I think I have nearly all code changes/fixes now. Will need to clean them up a bit and submit pull requests then.

T_XThe <a href="https://chaos.social/tags/VLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VLAN</a> code in the <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> bridge gives me some headaches. Took me a while to get why two brmctx <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> contexts are created, one for the untagged VLAN 0, one for the PVID 1. But only the former would be used, with brmctx->vlan not set, even though VLANs were configured. Turns out you need to not only enable multicast_snooping but also mcast_vlan_snooping. And confusingly, only the former is in sysfs. Seems like "ip link" is the most complete thing now, not "brctl", "bridge" tool or sysfs

T_XIn the classic, non-DSA <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> bridge the philosophy so far is: No matter in what combination you enable/disable multicast_snooping+ multicast_querier: The bridge ensures you don't break any network protocol, it detects per protocol family if <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> snooping is applicable. That together with <a href="https://chaos.social/tags/RFC4541" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC4541</a> I think is the only way to regain trust for <a href="https://chaos.social/tags/IGMP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IGMP</a> / <a href="https://chaos.social/tags/MLD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MLD</a> snooping imo. And now things like <a href="https://chaos.social/tags/DSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DSA</a> or <a href="https://chaos.social/tags/switchdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switchdev</a> come along with non-foolproof solutions, diverging between each driver...

T_XNeither <a href="https://chaos.social/tags/switchdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#switchdev</a> nor <a href="https://chaos.social/tags/DSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DSA</a> really check if an IGMP/MLD querier exists. So if you enable <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> snooping on these you currently also need to make sure to have an <a href="https://chaos.social/tags/IGMP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IGMP</a> / <a href="https://chaos.social/tags/MLD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MLD</a> querier somewhere. Which is different to a classic Linux bridge, which will stop snooping optimizations if there is none, to avoid packet loss. Only for Marvell Prestera I found some mrouter-exists check via an according switchdev event. Which no other driver uses. And...

T_X<a href="https://mastodon.social/@joemj" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@joemj</a> sehr schöner, gut zusammefassender Beitrag. Würde höchstens noch den "neuen" Ansatz "<a href="https://chaos.social/tags/AirtimeFairness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AirtimeFairness</a>" hinzupacken: Dass jede Station gleichviel Sendezeit statt gleichviel "Bandbreite"/Durchsatz bekommt, wie es unter <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> seit einer Weile mehrere <a href="https://chaos.social/tags/WLAN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WLAN</a> Treiber machen. Das sollte den letzten Punkt am Ende bzgl. Nachteile von <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a>-to-unicast stark abschwächen. Auch in <a href="https://chaos.social/tags/ForwardErrorCorrection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ForwardErrorCorrection</a> durch zB <a href="https://chaos.social/tags/RaptorQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaptorQ</a> für <a href="https://chaos.social/tags/RTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RTP</a> streams sehe ich große Chancen und es geht schon mit <a href="https://floss.social/@gstreamer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gstreamer</a>

John Heinrich<a href="https://mastodon.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a>-<a href="https://mastodon.social/tags/WiFi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WiFi</a>-Murmeltiertag.<a href="https://wirelesslywired.com/2019/05/02/multicast-over-wireless/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://wirelesslywired.com/2019/05/02/multicast-over-wireless/</a>

T_X<a href="https://det.social/@flori_man" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@flori_man</a> außerdem ist Unicast ja eigentlich eine Untermenge von <a href="https://chaos.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a>. Dh. wenn wir dessen extra Komplexität irgendwann mal in den Griff bekommen sollten, sehe ich da zumindest keinen Nachteil, das zu haben. Und es wäre ein weiteres Angebot, das <a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freifunk</a> von einem normalen Internetanschluss abheben könnte. Sonst meckern immer alle/viele, das sie in der Praxis nix neues von <a href="https://chaos.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Freifunk</a> gegenüber ihrem herkömmlichen, gekauften Internet hätten :D.

Recent searches

Search options

Administered by:

Server stats:

#multicast