#multicast — Public Fediverse posts

Multicast TV Distribution on My Home Network

https://www.apalrd.net/posts/2026/isp_mcast/

Comments: https://news.ycombinator.com/item?id=49051463

#HackerNews #Multicast #TV #HomeNetwork #Streaming #Tech #Guide

BgpLookup, a web service I wrote that displays the relationships between ASes and prefixes, now also shows multicast.

#dn42 #IPv6 #Multicast

OpenPGM: зачем Бирже мультикаст?

Существует два фундаментальных подхода к доставке данных: уникаст - передача "точка-точка", и мультикаст - передача "один-ко-многим". Подавляющее большинство данных в локальных и глобальных сетях ходит по TCP, уникасту. У большинства программистов сложилась четкая ассоциация: если нужно устроить сетевое взаимодействие, то используем TCP. Но в финансовой сфере на этот счёт мы привыкли думать по-другому. Если требуется построить систему с минимальным временем отклика, но при этом с высокой пропускной способностью и надежной доставкой, то мультикаст годится лучше.

https://habr.com/ru/companies/moex/articles/1044130/

#openpgm #rdma #pgm #multicast #мультикаст #биржа #фондовая_биржа

It's interesting how ass Windows is to use when it comes to low level networking. Nothing works as expected or how it works elsewhere.

In this case I'm trying to stream audio to a multicast address. Sure, the audio arrives, but it arrives in clumps every 300-1000 ms, not as a, well, smooth stream. Cue and endless search to try to find some option that would work around the idiotic Windows kernel's ideas. Still searching and hating this utter shit.

#windows #garbage #multicast #streaming

they think they found the issue.

here is their reply:

"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".

The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.

The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."

I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed