# multicast Published articles for multicast. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## KPN Interactieve TV zonder Experia Box DevFeed: [KPN Interactieve TV zonder Experia Box]() Original publisher: [Read original article]() Published: 2026-06-07T10:36:42Z Content type: tutorial Language: nl Sources: [Bert Hubert's writings]() Topics: [multicast](), [DHCP](), [Linux](), [Script](), [Internet](), [proxy](), [Raspberry Pi]() Tags: [dhcp](), [internet](), [linux](), [multicast](), [pi](), [pppoe](), [proxy](), [script](), [vlan](), [vlans]() ### AI overview This tutorial explains how to use a KPN Interactieve TV Set Top Box without an Experia Box. It describes the required KPN VLANs, multicast and IGMP proxy setup, DHCP option 60, and a Linux script that can run even on a Pi Zero. The author notes that the instructions were updated in June 2026 and includes a factory-reset tip. ### Source excerpt Ik ben een heel tevreden klant van KPN Internet. Om diverse redenen gebruik ik de Experia Box niet, maar ik wil wel graag TV kunnen kijken met de KPN Interactieve TV Set Top Box ("5202"). Vroeger ging dat "vanzelf goed", tegenwoordig is daar wat werk voor nodig. UPDATE Juni 2026 (na 5 jaar!): de instructies werken weer, er is een update geweest in het igmpproxy.conf bestand. Ook heb ik een tip toegevoegd hoe de ontvanger terug te brengen naar fabrieksinstellingen, wat bij mij recent nodig was. ## Testing IP Multicast with netlab DevFeed: [Testing IP Multicast with netlab]() Original publisher: [Read original article]() Published: 2025-11-26T06:56:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Routing (disambiguation)](), [Testing](), [GitHub]() Tags: [github](), [ip](), [multicast](), [netlab](), [permission](), [routing](), [tcp-ip](), [testing](), [volume](), [worth-reading]() ### AI overview The article highlights Aleksandr Albin's nearly 20-router lab topology for practicing inter-AS IP multicast. The topology and additional configuration templates are published on GitHub, with the experience also documented in a LinkedIn post. ### Source excerpt Aleksandr Albin built a large (almost 20-router) lab topology (based on an example from Jeff Doyle's Routing TCP/IP Volume 2) that he uses to practice inter-AS IP multicast. He also published the topology file (and additional configuration templates) on GitHub and documented his experience in a LinkedIn post. Lab topology, copied with permission by Aleksandr Albin It's so nice to see engineers using your tool in real-life scenarios. Thanks a million, Aleksandr, for sharing it. ## Espressif Thread Border Router DevFeed: [Espressif Thread Border Router]() Original publisher: [Read original article]() Author: John Lee Published: 2023-06-14T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [networking](), [ESP-IDF](), [Matter]() Tags: [announce](), [blog](), [border-router](), [development-kit](), [discovery](), [esp-idf](), [esp32](), [espressif](), [ethernet](), [iot](), [ipv4](), [matter](), [multicast](), [open-thread](), [thread](), [wi-fi]() ### AI overview Espressif's Thread Border Router solution received Thread Group certification, and its accompanying development kit was officially released. The article describes its ESP-IDF-based architecture, networking components, and features including IPv6 connectivity, service discovery, multicast forwarding, and NAT64. ### Source excerpt We are glad to announce that the Espressif Thread Border Router (ESP Thread BR) solution has received certification from the Thread Group, and the accompanying development kit has now been officially released. This blog post will delve into the technical aspects of the solution and explore the benefits it offers, facilitating faster time-to-market for our customers' products. ## Flow Control in Aeron DevFeed: [Flow Control in Aeron]() Original publisher: [Read original article]() Author: Michael Barker (noreply@blogger.com) Published: 2020-03-19T22:20:00Z Content type: tutorial Language: en Sources: [Bad Concurrency]() Topics: [networking](), [Messaging](), [Protocol (disambiguation)](), [Development]() Tags: [distributed-system](), [messaging](), [multicast](), [networking](), [protocol](), [udp]() ### AI overview This article explains flow control in Aeron, focusing on sliding-window behavior over UDP. It compares Aeron's receiver status messages with TCP acknowledgements and describes how receiver-window limits help prevent senders from overrunning receivers and causing message loss. ### Source excerpt One of my more recent projects has led me to become more involved in the Aeron project. If you are unaware of Aeron, then head over to the Github site and check it out. At its core is an reliable messaging system that works over UDP, Multicast UDP and IPC. It also contains an archiving feature for recording and replay and (still under active development) an implementation of the Raft protocol for clustering. Did I mention that it was fast too. I've spent the last few weeks buried in the various strategies the Aeron has for flow control. Specifically modifying the existing flow control strategies and adding more flexible configuration on a per channel basis. Before I jump into that it would be useful to cover a little background first. What is flow control? Within a distributed system the purpose of flow control is to limit the rate of a sender so that is does not overrun it's associated receiver. UDP does not come with any form of flow control, therefore it is easy to create a sender that will out pace the receiver, leading to message loss. There are a number of different forms of flow control, but I'm going to focus on the sliding window flow control protocol used by TCP and Aeron. The sliding window protocol requires that the sender maintain a buffer of data (referred to as a window). The size of this window will typically communicated from the receiver to the sender as part of the protocol. With a bi-directional protocol like TCP the size of the window is communicated in each TCP segment header. This is the amount of data that the sender can transmit to the receiver before having to wait until an acknowledgement is received. If the application thread on the receiver side is busy and does not read the data from the socket and the sender continues to transmit, the window size value will decrease until it reaches 0, at which time the sender must stop and wait for an acknowledgement with a non-zero window size before sending again. There is a lot more networking theo ## Java 9 Flow API: Multicasting via a Processor DevFeed: [Java 9 Flow API: Multicasting via a Processor]() Original publisher: [Read original article]() Author: David Karnok (noreply@blogger.com) Published: 2017-12-14T13:20:00Z Content type: tutorial Language: en Sources: [Akarnokd - Advanced RxJava]() Topics: [Java](), [Java 9](), [reactive](), [Streams](), [implementation](), [API]() Tags: [backpressure](), [cancellation](), [concurrency](), [flow](), [flow-api](), [java](), [java-9](), [jdk](), [multicast](), [processor](), [reactive](), [reactive-streams](), [streams](), [subscriber](), [subscription](), [tck]() ### AI overview This tutorial explains how Java 9 Flow API processors can multicast elements from a single upstream source to multiple consumers. It focuses on coordinating subscriber demand, backpressure, dynamic subscription, and cancellation, and introduces MulticastProcessor as the intermediate solution. ### Source excerpt Introduction There are situations when the same elements of a source should be dispatched to multiple consumers. Certainly, if the source supports multiple subscribers and is deterministic (such as our previous async range), one can just instantiate the flow multiple times. However, if the source doesn't support multiple subscribers or each subscription ends up being unique and/or non-deterministic, that simple approach doesn't work anymore. We need a way to have a single realization of the (upstream) source yet allow multiple consumers. Since we are dealing with Flow.Publishers that require backpressure management, such intermediate solution has to coordinate requests from its Flow.Subscribers in addition to handling the dynamic subscription and unsubscription (cancellation) of said Flow.Subscribers while the flow is active. Enter, MulticastProcessor. Flow.Processor recap What is a Processor? By definition, it is a combination of a Flow.Publisher and a Flow.Subscriber, i.e., it can act as a source and can be subscribed to via subscribe() as well as the processor itself can be used with somebody else's Flow.Publisher.subscribe(). It has a mixed history as the idea comes from the original Observer pattern (i.e., java.util.Observable) and Rx.NET's Subject that allows dispatching signals to multiple Observers in an imperative (and synchronous) fashion. The Flow.Processor in Java 9 defines two type arguments, one for its input side (Flow.Subscriber) and one for its output side (Flow.Publisher). The idea behind it was that a Flow.Processor can act as a transformation step between an upstream and a downstream. However, such transformation often mandates the Flow.Processor implementation only accepts a single Flow.Subscriber during its entire lifetime. Since the implementation has to follow the Reactive Streams specification nonetheless, this adds a lot of overhead to the flow. As demonstrated in previous posts, when a flow is realized, there are only one subscriber per st ## What the interns have wrought, 2017 edition DevFeed: [What the interns have wrought, 2017 edition]() Original publisher: [Read original article]() Author: Yaron Minsky Published: 2017-08-14T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [Development](), [networking](), [Database](), [Caching](), [Monitoring]() Tags: [algorithms](), [api](), [caching](), [database](), [infrastructure](), [internship](), [monitoring](), [multicast](), [networking](), [ocaml](), [servers](), [snapshots](), [tracing]() ### AI overview A retrospective on Jane Street's 2017 development interns, highlighting projects involving packet-capture databases, message-rate visualization, tracing tools, OCaml APIs, scheduling algorithms, and network-switch monitoring. It also introduces market data feeds and the need for gap-fillers and snapshot servers. ### Source excerpt Intern season is coming to a close, and it's a nice time to look back (as I've done in previous years) and review some of what the interns did while they were here. The dev intern program has grown considerably, with almost 40 dev interns between our NY, London, and Hong Kong offices.