> 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/faq/sdk/does-ndi-prevent-multicast-address-and-port-conflicts-when-using-a-shared-multicast-ip-pool.md).

# Does NDI prevent multicast address and port conflicts when using a shared multicast IP pool?

The NDI sender chooses which multicast addresses it will use. Given the `netprefix` and `netmask` values, it randomly picks a set of addresses to use. This part is important. It does not pick a single address per sender. It picks multiple addresses.

Ideally, the range defined by the `netprefix` and `netmask` is large enough to accommodate usage across the whole network. For example, a network with 32 encoders and a multicast range of 32 addresses would not be sufficient.

NDI does not have a mechanism to avoid conflicts. There is an identifier within the multicast streams themselves, but if two NDI senders choose the same multicast address, the receiving side could potentially subscribe to both streams and then pick out the correct data. This is not ideal, since it would need to receive both streams in order to discard one.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ndi.video/all/faq/sdk/does-ndi-prevent-multicast-address-and-port-conflicts-when-using-a-shared-multicast-ip-pool.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.