So I tried to document a potential pitfall with layer 3 #multicast routing, with #PIM in particular, here: https://wiki.dn42.dev/howto/pim-multicast-vs-unicast-issue
The issue of multicast potentially being black holed if the unicast topology is larger than the potential multicast one. I'm wondering how other people tackle or avoid this or if I'm missing an easy solution.
(I'm wondering if maybe @troglobit or @dentangle might have some ideas?)
Esther Payne :bisexual_flag:
boosted
@OlivierAuber hum - AGI is a mirage we should not seek to catch.
human intelligence in a society helped with communication tech is, But indeed it's captured now for decades.
#Multicast is not profiting authoritarianism in any way, so I would really not bet huawei is going to invest in it either. It needs multipolar worlds entities collaborating together, not competing for power. This could come if ppl awake from the current slopness (as a next history wave)
imho it was not a effective stage
@olm_e @OlivierAuber Agreed. While we're waiting for the AI/LLM bubble to pop lets keep building the systems we need to help society recover from the mess that will be left behind.
#Multicast can help us build truly decentralized systems that do not rely on the same centralized, profit-driven corporations that are stoking this AI/LLM bubble.
@OlivierAuber hum - AGI is a mirage we should not seek to catch.
human intelligence in a society helped with communication tech is, But indeed it's captured now for decades.
#Multicast is not profiting authoritarianism in any way, so I would really not bet huawei is going to invest in it either. It needs multipolar worlds entities collaborating together, not competing for power. This could come if ppl awake from the current slopness (as a next history wave)
imho it was not a effective stage
Ma discussion "au coin du feu" avec Ben Goertzel au #BGIsummit Istanbul
I reclaim the original DISTRIBUTED architecture of the internet
"CISCO, why not opening #Multicast for #SingularityNet #agi
Et j'ai ajouté en off : "If CISCO don't, Huawei will"
https://www.youtube.com/live/gb5ESFppdD8?si=iHr6wGPYHmwdX4cB&t=11704
🫧 socialcoding..
boosted
I wonder if @librecast has some plans or even a lobby in the EU to advance the adoption of #Multicast in the near future. If there's any time the @EU_Commission would be interested in a major technological shift (due to digital sovereignity efforts) it's probably right now.
To my understanding the underlying capabilities (below layer 5) are already there, it really just needs the political will to enforce it being enabled in routers etc.
Or are there still big fundamental hurdles? 🤔 @dentangle
I wonder if @librecast has some plans or even a lobby in the EU to advance the adoption of #Multicast in the near future. If there's any time the @EU_Commission would be interested in a major technological shift (due to digital sovereignity efforts) it's probably right now.
To my understanding the underlying capabilities (below layer 5) are already there, it really just needs the political will to enforce it being enabled in routers etc.
Or are there still big fundamental hurdles? 🤔 @dentangle
Alex Akselrod
and 1 other
boosted
We've got some good news thanks to @nlnet and @NGIZero 🎉
Librecast has been funded to do more awesome things with #multicast
Watch this space.
We've got some good news thanks to @nlnet and @NGIZero 🎉
Librecast has been funded to do more awesome things with #multicast
Watch this space.
Had an interesting conversation with someone from the IETF about #multicast 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 #Librecast built a demo for back in 2022 as part of #NGI0Discovery and which we're working on again now as part of #NGI0Core thanks to @nlnet so I think we might be able to help.
We've got a new tool! lcagent version 0.1.0, the #Librecast #multicast 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 #RaptorQ using Librecast’s liblcrq library to provide forward error correction in the event of packet loss.
lcagent can be used to send and receive data over #multicast 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.
#librecast
We've got a new tool! lcagent version 0.1.0, the #Librecast #multicast 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 #RaptorQ using Librecast’s liblcrq library to provide forward error correction in the event of packet loss.
Je trie mes vieux cartons :
#collector ! Il y a trente ans, Francis Mizio raconte comment il été pris d'une sorte de frayeur cosmique lors de la première expérience planètaire temps réel de la version distribuée #multicast du #poieticgenerator
@dlakelan @mray 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 #multicast but it doesn't meet #Librecast 's requirements.
@mray 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 #multicast 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.
It'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.
Use #BSD for good networking, nuff said... Use #OPNsense for a firewall/router, nuff said...
Me trying to use #multicast snooping with this in our hackspace: After several hours of debugging, realizing it's not bc. of the #OpenWrt powered, #rtl83xx based switch I've added, nor the new patches I've made and added to it. But because of this two years old, ignored #OPNsense (or #FreeBSD?) bug with #MLD: https://github.com/opnsense/core/issues/6247
😒 😤
Every time I `git commit` now my computer is sending patches over #IPv6 #multicast to our CI system (a bunch of test machines and VMs running on qemu) and this is how development should be.
`git pull` ?! Pah! You unicast kids with your centralized servers! 😉