> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/developing-with-ndi/ndi-certified/certification-process/testing-methods/multicast-testing.md). # Multicast Testing With large and even mid-size NDI workflows, multicast is becoming more and more of a necessity in an environment where any video stream can be pulled by any receiver at any time. While multicast can be enabled, testing would require additional software. 1. Download and install Wireshark 2. Reduce the network connection to just a single NIC, coming from the network that the NDI device is on 3. Ensure that the switch the devices are connected to are managed, multicast capable, and have IGMP snooping enabled to prevent broadcast storms 4. Launch the NDI device or software, and enable Multicast 1. If this is from software that uses the NDI Access Manager to enable it, do the following: First, launch Access Manager 2. Navigate to the Advanced Tab, then click the Multicast dropdown button\ ![](https://3444609009-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDO9LSaUxLOBIgPjyrjR1%2Fuploads%2FJ684OZajD0FF6KyBEVru%2Fimage.png?alt=media\&token=1ecd2da2-4e05-48d0-a65e-47f7087482b6) 3. Check the box by IP. A warning will come up that doing so could cause consequences on an improperly managed network. Press OK to dismiss that message\ ![](https://3444609009-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDO9LSaUxLOBIgPjyrjR1%2Fuploads%2ForkwyygmKGhOsPkQfuGo%2Fimage.png?alt=media\&token=75812f0f-76a6-4b16-890b-ffc09fc6a82e) 4. Unless you know the IP and address, Mask, and TTL values to use, leave it as-is 5. Press OK to save your changes, then Launch your NDI device device or software 5. Launch Wireshark on the receiving PC, and double click the interface that's receiving the connection. In my example, I'm clicking Ethernet, as that has active data. \ ![](https://3444609009-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDO9LSaUxLOBIgPjyrjR1%2Fuploads%2Fr4BjuZP2zdXYgU1syi89%2Fimage.png?alt=media\&token=d45ea757-b708-41fc-90bd-f7e780dc3047) 6. If the only two devices are this network are the receive and sender in multicast, you should see the data flow look like the below picture. The important things to note are 1. The Source IP is the IP of the device that's sending Multicast 2. The Destination IP is a reserved multicast IP (). If the destination IP is the local IP of the system running Wireshark, then it's not a multicast stream 3. Typically, the transmit data for multicast is UDP If the protocol shown is TCP, then it's not multicast \ ![](https://3444609009-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDO9LSaUxLOBIgPjyrjR1%2Fuploads%2FfjDwneX3u89ZwkZtNZFJ%2Fimage.png?alt=media\&token=b5e4b684-4cf1-4897-a19f-48b27090f0b5) 7. If there's too much data from other programs or devices on the network or machines and you need to isolate to just the sending system, use the filters for multicast: ip.addr==IP ADDRESS\ 8. Disable multicast and view the Wireshark output- it should change the Destination address to the local IP and may change the protocl to TCP. Re-enabled multicast and confirm it changes back 9. Restart the device and confirm the test again.\
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ndi.video/all/developing-with-ndi/ndi-certified/certification-process/testing-methods/multicast-testing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.