Dante Multicast Address Range: Plan, Verify, and Troubleshoot Flows

TL;DR — A multicast address identifies a destination group; it does not identify a single receiver or guarantee that switches forward the stream correctly. Record the range and allocation method used by the actual Dante devices and management tools, keep it separate from other managed multicast pools, map every address to its flow and channels, then verify joins, link scope, audio, removal, and recovery. Never invent or manually reuse an address because it appears unused.

Separate the address from the audio route

A Dante multicast flow sends one media stream to a multicast group address. Interested receivers join that group, while the network's snooping and querier design controls where the traffic is forwarded. The address is therefore one part of a larger route.

The multicast flow setup guide explains how to create the flow. This article owns address-pool planning and conflict diagnosis.

Use the documented range for the deployed system

Multicast ranges and allocation controls can depend on the Dante product, firmware, management environment, AES67 mode, and network design. Use the range displayed or specified by the current supported tools and manufacturer documentation. Do not copy a prefix from another venue or an old project without verifying it.

When a site carries several multicast systems, assign ownership for each pool. Document Dante, AES67, video, control, paging, and corporate multicast ranges together so separate teams do not allocate the same group for unrelated traffic.

Build an address inventory

1. Export or record every existing multicast flow before adding one.
2. Capture its transmitter, channels, format, group address, receivers, VLAN, and owner.
3. List other multicast pools active on the same routed or switched domain.
4. Mark reserved, managed, and dynamically allocated ranges according to the site standard.
5. Identify trunks and uplinks that can carry more than one production system.
6. Save switch membership and utilization evidence for the healthy baseline.

Treat the inventory as operational data, not merely an IP spreadsheet. A valid address with the wrong channels or forwarding scope is still a bad route.

Allocate through the supported workflow

Let Dante Controller, Dante Domain Manager, or the applicable device workflow allocate and manage the group according to the supported design. If a managed environment allows a custom range, validate the complete pool against the site's multicast plan before changing it.

Do not manually assign a group already used by another sender. Two unrelated streams sharing one destination group can produce unexpected traffic, receiver confusion, excess load, or audio failure even when each transmitter appears healthy in isolation.

Verify scope after creating a flow

Confirm the address-to-flow map

Record the assigned address, transmitter, channel order, format, and intended receivers immediately after creation. Avoid identifying a flow by address alone; the map must connect it to named audio.

Inspect membership and forwarding

Confirm only the intended receiver-facing ports join the group. Verify the querier is stable and traffic crosses only the required trunks and uplinks. The IGMP snooping and querier guide covers membership control.

Prove the physical destinations

Send identifiable audio through each channel and confirm receiver mapping, level, and final output. Then run the expected production load while watching link utilization and errors. The multicast bandwidth guide covers capacity evidence.

Diagnose an address conflict methodically

Capture the group at the transmitter-facing and receiver-facing ports when permitted. Compare source address, destination group, packet rate, and channel timing. Change one boundary at a time; repeatedly deleting and recreating flows can hide the original conflict.

Test removal and recovery

1. Start representative audio and capture memberships, port rates, and receiver output.
2. Remove one approved receiver subscription and verify its membership leaves without affecting others.
3. Restore the subscription and confirm the same named channels return correctly.
4. Remove the test flow using the supported workflow.
5. Verify traffic stops on every carried link and the address is no longer mapped to an active flow.
6. Recreate only if required, then test restart persistence and the documented rollback.

Allow the network's documented leave and membership timers to operate before declaring stale traffic.

Multicast address acceptance checklist

• The active range and allocation owner are documented from current tools.
• Dante and other multicast pools do not overlap unintentionally.
• Every active address maps to one named transmitter, flow, and channel set.
• Intended receivers and physical destinations are recorded.
• Membership and forwarding scope match the design.
• Trunks and uplinks remain within the accepted bandwidth budget.
• Identifiable audio passes through every mapped channel.
• Removal, leave behavior, restoration, restart, and rollback are tested.
• The owner and accepted evidence are included in the handoff.

Document the multicast handoff

Record the address pool, allocator, VLAN, active groups, transmitters, channels, receivers, switch path, querier, membership evidence, utilization, test results, owner, removal procedure, and rollback. Update the map whenever a flow changes.

Keep the accepted multicast map beside the digital patch and input list in Techrider.live. Invite collaborators to edit the same rider, save the tested revision, inspect history, and export a current PDF for the venue, broadcast, or touring team.

FAQ

What multicast address range does Dante use?

Use the range reported or documented for the exact Dante devices, firmware, and management environment. Do not assume one copied prefix applies to every deployment or interoperability mode.

Can I change the Dante multicast address range?

Some managed environments may expose supported range controls. Validate any proposed pool against the complete site multicast plan and follow the current product documentation before changing it.

How do I find the IP address of a Dante multicast flow?

Inspect the flow in the supported Dante management tool and correlate it with switch membership or an approved packet capture. Record the transmitter and channels with the address.

Can two audio systems use the same multicast address?

They should not send unrelated traffic to the same group within a shared multicast scope. Assign non-overlapping pools and verify routed boundaries so one system cannot collide with another.

How do I troubleshoot a Dante multicast address conflict?

Map active groups to transmitters, compare switch memberships and captures at both ends, rule out clock and format faults, remove one controlled source or subscription, and verify that traffic and audio change exactly as expected.