#multicast — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #multicast, aggregated by home.social.
-
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.
-
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.
-
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.
-
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.
-
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.
-
NETGEAR Insights: The Growing Importance of AV-IT Convergence in Enterprises
#TycoonWorld #AVITConvergence #DigitalTransformation #EnterpriseTechnology #FutureReady #NetworkingSolutions #AVoverIP #AVoIP #SmartWorkspaces #DigitalInfrastructure #ITInfrastructure #UnifiedCommunications #EnterpriseNetworking #ProAV #NetworkPerformance #LowLatency #HighBandwidth #PoE #Multicast #CyberSecurity #NetworkSecurity #IPBasedSystems #ScalableSolutions
https://tycoonworld.in/netgear-insights-the-growing-importance-of-av-it-convergence-in-enterprises/
-
NETGEAR Insights: The Growing Importance of AV-IT Convergence in Enterprises
#TycoonWorld #AVITConvergence #DigitalTransformation #EnterpriseTechnology #FutureReady #NetworkingSolutions #AVoverIP #AVoIP #SmartWorkspaces #DigitalInfrastructure #ITInfrastructure #UnifiedCommunications #EnterpriseNetworking #ProAV #NetworkPerformance #LowLatency #HighBandwidth #PoE #Multicast #CyberSecurity #NetworkSecurity #IPBasedSystems #ScalableSolutions
https://tycoonworld.in/netgear-insights-the-growing-importance-of-av-it-convergence-in-enterprises/
-
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
-
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
-
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
-
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
-
GOD DAMN IT:
https://www.libertysys.com.au/2022/12/pain-points-mld-snooping-on-linux-bridges/
There's a bug in #multicast snooping that breaks neighbor discovery, and apparently #proxmox enables snooping by default on bridges... This is causing all my headaches! and it's an OLD bug from back in 2013 or more! #librecast @librecast
do you guys know anything about this?
-
GOD DAMN IT:
https://www.libertysys.com.au/2022/12/pain-points-mld-snooping-on-linux-bridges/
There's a bug in #multicast snooping that breaks neighbor discovery, and apparently #proxmox enables snooping by default on bridges... This is causing all my headaches! and it's an OLD bug from back in 2013 or more! #librecast @librecast
do you guys know anything about this?
-
GOD DAMN IT:
https://www.libertysys.com.au/2022/12/pain-points-mld-snooping-on-linux-bridges/
There's a bug in #multicast snooping that breaks neighbor discovery, and apparently #proxmox enables snooping by default on bridges... This is causing all my headaches! and it's an OLD bug from back in 2013 or more! #librecast @librecast
do you guys know anything about this?
-
GOD DAMN IT:
https://www.libertysys.com.au/2022/12/pain-points-mld-snooping-on-linux-bridges/
There's a bug in #multicast snooping that breaks neighbor discovery, and apparently #proxmox enables snooping by default on bridges... This is causing all my headaches! and it's an OLD bug from back in 2013 or more! #librecast @librecast
do you guys know anything about this?
-
GOD DAMN IT:
https://www.libertysys.com.au/2022/12/pain-points-mld-snooping-on-linux-bridges/
There's a bug in #multicast snooping that breaks neighbor discovery, and apparently #proxmox enables snooping by default on bridges... This is causing all my headaches! and it's an OLD bug from back in 2013 or more! #librecast @librecast
do you guys know anything about this?
-
Yes, it disappears and then I can't ND to the router, and ping won't work.
Why does the #linux bridge lose track of the fact the router wants that #multicast group?
-
Yes, it disappears and then I can't ND to the router, and ping won't work.
Why does the #linux bridge lose track of the fact the router wants that #multicast group?
-
Yes, it disappears and then I can't ND to the router, and ping won't work.
Why does the #linux bridge lose track of the fact the router wants that #multicast group?
-
Yes, it disappears and then I can't ND to the router, and ping won't work.
Why does the #linux bridge lose track of the fact the router wants that #multicast group?
-
Yes, it disappears and then I can't ND to the router, and ping won't work.
Why does the #linux bridge lose track of the fact the router wants that #multicast group?
-
-
-
-
-
So having cables plugged in to the router will successfully deliver the packets to the devices. But not on wlan on the same router. Any settings on the router related to multicast such as igmp snooping is set correctly as far as I understand #IPv6 #multicast
-
So having cables plugged in to the router will successfully deliver the packets to the devices. But not on wlan on the same router. Any settings on the router related to multicast such as igmp snooping is set correctly as far as I understand #IPv6 #multicast
-
So having cables plugged in to the router will successfully deliver the packets to the devices. But not on wlan on the same router. Any settings on the router related to multicast such as igmp snooping is set correctly as far as I understand #IPv6 #multicast
-
So having cables plugged in to the router will successfully deliver the packets to the devices. But not on wlan on the same router. Any settings on the router related to multicast such as igmp snooping is set correctly as far as I understand #IPv6 #multicast
-
This is really fucking annoying tbh #IPv6 #multicast
-
This is really fucking annoying tbh #IPv6 #multicast
-
-
This is really fucking annoying tbh #IPv6 #multicast
-
Besides the crates not supporting receiving multicast messages it seems there might also be an issue where my router isn’t sending the packets on the wireless links #IPv6 #multicast
-
Besides the crates not supporting receiving multicast messages it seems there might also be an issue where my router isn’t sending the packets on the wireless links #IPv6 #multicast
-
Besides the crates not supporting receiving multicast messages it seems there might also be an issue where my router isn’t sending the packets on the wireless links #IPv6 #multicast
-
Besides the crates not supporting receiving multicast messages it seems there might also be an issue where my router isn’t sending the packets on the wireless links #IPv6 #multicast
-
Narrowing it down to possibly esp-hal not fully supporting setting the options to set the interface to listen to the multicast group. #RustLang #multicast #smoltcp
-
Narrowing it down to possibly esp-hal not fully supporting setting the options to set the interface to listen to the multicast group. #RustLang #multicast #smoltcp
-
Narrowing it down to possibly esp-hal not fully supporting setting the options to set the interface to listen to the multicast group. #RustLang #multicast #smoltcp
-
Narrowing it down to possibly esp-hal not fully supporting setting the options to set the interface to listen to the multicast group. #RustLang #multicast #smoltcp
-
@voided Are you aware that depending on the router (or it's settings) #multicast may not work that well on WiFi?
-
@voided Are you aware that depending on the router (or it's settings) #multicast may not work that well on WiFi?
-
@voided Are you aware that depending on the router (or it's settings) #multicast may not work that well on WiFi?
-
@voided Are you aware that depending on the router (or it's settings) #multicast may not work that well on WiFi?
-
@voided Are you aware that depending on the router (or it's settings) #multicast may not work that well on WiFi?
