det.social

Hacker NewsAeron: Efficient reliable UDP unicast, UDP multicast, and IPC message transport<a href="https://github.com/aeron-io/aeron" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/aeron-io/aeron</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/Aeron" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Aeron</a> <a href="https://mastodon.social/tags/UDP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UDP</a> <a href="https://mastodon.social/tags/transport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transport</a> <a href="https://mastodon.social/tags/Efficient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Efficient</a> <a href="https://mastodon.social/tags/Reliable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Reliable</a> <a href="https://mastodon.social/tags/IPC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPC</a> <a href="https://mastodon.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a>

T_X<a href="https://social.ffmuc.net/@freifunkMUC" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@freifunkMUC</a> war zumindest bei Audio sehr begeistert von <a href="https://chaos.social/tags/RaptorQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaptorQ</a>, einem <a href="https://chaos.social/tags/ForwardErrorCorrection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ForwardErrorCorrection</a> (<a href="https://chaos.social/tags/FEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FEC</a>) Mechanismus, für den es auch einen <a href="https://chaos.social/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> gibt (falls es bei euch überhaupt mit packetloss auf der Strecke zusammenhängen sollte): <a href="https://www.rfc-editor.org/rfc/rfc6330" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.rfc-editor.org/rfc/rfc6330</a> Wird aber leider bisher nur von <a href="https://floss.social/@gstreamer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gstreamer</a> über ein <a href="https://chaos.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> plugin unterstützt, <a href="https://floss.social/@videolan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@videolan</a> kann das leider noch nicht.Hm, das wäre doch auch nochmal ein lustiger Testcase für die neuen <a href="https://chaos.social/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a> features mit <a href="https://chaos.social/tags/Gluon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gluon</a> + <a href="https://social.freifunk.net/@batadv" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@batadv</a> :-).

Waidler :mastodon:Endlich funktioniert die Endpoint-Erkennung VLAN-übergreifend wieder bei meinem ROON Server. ROON hätte gerne alle Klienten im gleichen Netzwerksegment. Dann klappt die Erkennung auf Anhieb. Bei mehreren VLANs wird's dann schwierig. Da muß man tiefer in die Trickkiste bei den Multicast-Einstellungen greifen. Alte Firewallregeln in der OPNsense-Firewall entfernt und gut durchdachte neue hinzugefügt und schon funktioniert es wieder VLAN-übergreifend.<a href="https://bayerwald.social/tags/roon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#roon</a> <a href="https://bayerwald.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> <a href="https://bayerwald.social/tags/firewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firewall</a> <a href="https://bayerwald.social/tags/opnsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opnsense</a> <a href="https://bayerwald.social/tags/mdns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mdns</a>

LibrecastWe've got some good news thanks to <a href="https://social.nlnet.nl/@nlnet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nlnet</a> and <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@NGIZero</a> 🎉 Librecast has been funded to do more awesome things with <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> Watch this space.<a href="https://chaos.social/tags/ngi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ngi</a> <a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librecast</a> <a href="https://spectra.video/w/fyecXM9ULjsKDpUN3bMiid" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://spectra.video/w/fyecXM9ULjsKDpUN3bMiid</a>

just small circles 🕊<a href="https://social.tchncs.de/@mray" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mray</a> <a href="https://social.coop/@cwebber" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cwebber</a> would love to know as well.For people not in the know, <a href="https://chaos.social/@librecast" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@librecast</a> is a R&D initiative that's innovating the internet stack with support of <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@NGIZero</a> and <a href="https://social.nlnet.nl/@nlnet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nlnet</a> First, to enable <a href="https://social.coop/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> on the unicast internet an overlay network is planned, based on <a href="https://social.coop/tags/WebRTC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebRTC</a>. See:<a href="https://librecast.net/librecast-strategy-2025.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://librecast.net/librecast-strategy-2025.html</a><a href="https://social.coop/tags/Librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librecast</a> LIVE will bring all the technology together, to demonstrate and be a reference implementation. With <a href="https://social.coop/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> support being planned. See:<a href="https://librecast.net/live.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://librecast.net/live.html</a>

just small circles 🕊Dodge the dodgy <a href="https://social.coop/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a> infested corporate <a href="https://social.coop/tags/streaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#streaming</a> services and zoom out, as on the <a href="https://social.coop/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fediverse</a> we own the stream. Here are platforms that offer <a href="https://social.coop/tags/streaming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#streaming</a> of <a href="https://social.coop/tags/video" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#video</a> or <a href="https://social.coop/tags/audio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#audio</a> in real time or near real time, with live chat and other <a href="https://social.coop/tags/social" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#social</a> capabilities.On the fediverse our 💜 <a href="https://social.coop/tags/lifestreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lifestreams</a> meet people and humanity and we engage our favorite fedi crowds. Fedi is where outreach matters.<a href="https://social.coop/tags/Librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librecast</a> LIVE. <a href="https://chaos.social/@librecast" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@librecast</a> is a research project aiming to bring <a href="https://social.coop/tags/Multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Multicast</a> to the masses.<a href="https://social.coop/tags/Owncast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Owncast</a>. <a href="https://social.owncast.online/@owncast" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@owncast</a>

Brett Sheffield (he/him)Had an interesting conversation with someone from the IETF about <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> today.Some folks have been trying to solve the problem of getting multicast streams from unicast only sources (Off-net Sourcing) such as browsers.This happens to be something <a href="https://chaos.social/tags/Librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librecast</a> built a demo for back in 2022 as part of <a href="https://chaos.social/tags/NGI0Discovery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGI0Discovery</a> and which we're working on again now as part of <a href="https://chaos.social/tags/NGI0Core" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGI0Core</a> thanks to <a href="https://social.nlnet.nl/@nlnet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nlnet</a> so I think we might be able to help.

just small circles 🕊<a href="https://chaos.social/@librecast" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@librecast</a> <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@NGIZero</a> Congratulations on the release, <a href="https://social.coop/tags/Librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librecast</a> team! 🎉It is a very exciting <a href="https://social.coop/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> use case you are driving lcagent with, and I am looking forward to learn more about your experiences with this <a href="https://social.coop/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> setup.Thank you, for all the hard work!

Librecastlcagent can be used to send and receive data over <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> and to pipe data between programs on one computer and as many receivers as the multicast network can support simultaneously. We're currently using it now to run our own CI builds by multicasting the patch to multiple build servers simultaneously. This could also be useful for monitoring and configuration management. <a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librecast</a><a href="https://codeberg.org/librecast/lcagent" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/librecast/lcagent</a>This work is made possible by <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@NGIZero</a> <a href="https://chaos.social/tags/NGICore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGICore</a>

LibrecastWe've got a new tool! lcagent version 0.1.0, the <a href="https://chaos.social/tags/Librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librecast</a> <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> agent.In server mode, lcagent can be configured to listen on Librecast Channels (multicast groups) and execute programs in response to packet data received on those Channels.Packets must be accompanied by an authorized token and signed by the matching key or they will be silently dropped.Data is encoded with <a href="https://chaos.social/tags/RaptorQ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RaptorQ</a> using Librecast’s liblcrq library to provide forward error correction in the event of packet loss.

T_XHow I now imagine it when my laptop sends an <a href="https://chaos.social/tags/MLD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MLD</a> report to leave a specific <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> group: <a href="https://www.youtube.com/watch?v=jmzdObf3FtA" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=jmzdObf3FtA</a> "We're Not Gonna Take It (<a href="https://chaos.social/tags/MTG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MTG</a> Parody)" <a href="https://chaos.social/tags/MulticastTheGathering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MulticastTheGathering</a> <a href="https://chaos.social/tags/MagicTheGathering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MagicTheGathering</a>

Brett Sheffield (he/him)<a href="https://mastodon.sdf.org/@dlakelan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dlakelan</a> <a href="https://social.tchncs.de/@mray" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mray</a> You're technically correct (the best kind!)Yes, SSM is PULL rather than PUSH, so it has one of the properties of multicast, but it is lacking the other characteristics that make multicast special.SSM relies on knowing in advance the *unicast* IP address of the source.SSM is unidirectional.SSM lets one sender shout at everyone else.SSM is not group communication.SSM has its uses, and it's easier than true <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> but it doesn't meet <a href="https://chaos.social/tags/Librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librecast</a> 's requirements.

Brett Sheffield (he/him)<a href="https://social.tchncs.de/@mray" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mray</a> IP multicast is a complicated mess, largely because IP is fundamentally unicast in design. There are several different forms of ASM (Any Source Multicast) and most of the complexity is around building source trees when you don't know where the source(s) will be yet.SSM is a clever hack that says, what if we just skip past all that to the end when we KNOW who is sending, and build that, as it covers a lot of use cases (eg. ballgames).But, it loses most of what makes <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> special

Brett Sheffield (he/him)<a href="https://social.tchncs.de/@mray" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mray</a> Depends on your point of view. Streaming a ballgame to millions of viewers is a problem television solved over 70 years ago. We call that broadcast.If we use SSM (Single Source Multicast) to unidirectionally stream a game to millions of viewers, I call that broadcast, regardless of how many protocols we use that happen to have <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> in their name.Most IP multicast is actually broadcast.Multicast is group communication. If only one member of the group can speak, that's broadcast.

Brett Sheffield (he/him)Oops. I think I might have just told a well known person in the IP <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> world that SSM isn't multicast and that what they've built is "broadcast"...

T_XOh, ha, and speaking of <a href="https://chaos.social/tags/firewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firewall</a> + <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> fixes: Didn't notice before but my <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://chaos.social/tags/netfilter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netfilter</a> fix for <a href="https://chaos.social/tags/MRD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MRD</a> has made it upstream, yaiy: <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a3540a8bf3c13dc3955f0c0895332b9c653be3f" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a3540a8bf3c13dc3955f0c0895332b9c653be3f</a> It went in through net-next, so likely won't be backported to stable kernels. But now I'm looking forward to <a href="https://chaos.social/tags/Proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Proxmox</a> using Linux 6.10, then I can drop the workaround firewall rule on the <a href="https://social.chaotikum.org/@chaotikumev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chaotikumev</a> server.

T_XYaiy, nice, the ticket author of the MLD reports on wrong interface issue on <a href="https://chaos.social/tags/OPNsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPNsense</a> seems to have a lead! One more <a href="https://chaos.social/tags/firewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firewall</a> + <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> bug fixed soon? <a href="https://github.com/opnsense/core/issues/6247#issuecomment-2900111733" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/opnsense/core/issues/6247#issuecomment-2900111733</a>

LibrecastIt's a new release of Librecast! 🎉This release adds restricted channel support with token based authentication. This allows keyrings to be created and filters to be applied to channels such that any data arriving which is not signed and accompanied by a token issued by an authorised key will be dropped.This work is made possible by <a href="https://mastodon.xyz/@NGIZero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@NGIZero</a> as <a href="https://chaos.social/tags/NGICore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NGICore</a> <a href="https://lists.sr.ht/~librecast/librecast-announce/%3Cf47f0cae-8d06-48bc-b073-6559fdaf894d@librecast.net%3E" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lists.sr.ht/~librecast/librecast-announce/%3Cf47f0cae-8d06-48bc-b073-6559fdaf894d@librecast.net%3E</a><a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> <a href="https://chaos.social/tags/librecast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librecast</a>

T_XUse <a href="https://chaos.social/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> for good networking, nuff said... Use <a href="https://chaos.social/tags/OPNsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPNsense</a> for a firewall/router, nuff said...Me trying to use <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> snooping with this in our hackspace: After several hours of debugging, realizing it's not bc. of the <a href="https://chaos.social/tags/OpenWrt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenWrt</a> powered, <a href="https://chaos.social/tags/rtl83xx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rtl83xx</a> based switch I've added, nor the new patches I've made and added to it. But because of this two years old, ignored <a href="https://chaos.social/tags/OPNsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPNsense</a> (or <a href="https://chaos.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a>?) bug with <a href="https://chaos.social/tags/MLD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MLD</a>: <a href="https://github.com/opnsense/core/issues/6247" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/opnsense/core/issues/6247</a> 😒 😤

T_X<a href="https://bsd.network/@dch" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dch</a> <a href="https://mastodon.social/@RecoveredExpert" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@RecoveredExpert</a> let me know if you happen to find some peering partner for <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multicast</a> via <a href="https://chaos.social/tags/PIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PIM</a>, with an official, public AS. I had asked the <a href="https://mastodon.social/@DFN" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@DFN</a> via email months ago and asked again last month, if there were options to peer with them as a non-<a href="https://chaos.social/tags/DFN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DFN</a> member. But I still did not hear back from them. Other than that only building something ourself via <a href="https://chaos.social/tags/dn42" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dn42</a> comes to my mind: <a href="https://dn42.dev/Home" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://dn42.dev/Home</a> There used to be the <a href="https://chaos.social/tags/m6bone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#m6bone</a> project, but it is dead these days.

Recent searches

Search options

Administered by:

Server stats:

#multicast