Dante Controller Network Interfaces: Choose the Correct NIC

TL;DR — Dante Controller communicates through the computer interfaces assigned as its primary and secondary Dante connections. On a typical show network, select the wired adapter physically connected to Dante as primary; do not assume the operating system's default route is the same choice. For redundant systems, use separate NICs and switches for primary and secondary when available. Verify adapter name, link, IP scheme, interface role, and device visibility after docks, VPNs, or cabling change.

Interface selection defines Controller's network view

A production laptop may expose Ethernet, Wi-Fi, a USB dock, Thunderbolt Ethernet, VPN tunnels, virtual-machine adapters, and other interfaces. Dante Controller must know which adapter reaches the physical primary network and, if used, which separate adapter reaches secondary.

Controller remembers the selection. That is convenient until the laptop moves between systems or a dock is replaced.

Identify the adapter before selecting it

Do not choose “Ethernet” by label alone. Match four facts:

1. physical connector or dock port;
2. operating-system adapter name and hardware address;
3. link state and negotiated speed;
4. IP address and subnet expected on that Dante network.

Disconnecting and reconnecting the cable can help identify the changing link state during setup. Label production adapters and cables once confirmed.

Primary and secondary mean network roles

The primary selection is not merely the laptop's favorite route to the internet. It represents the computer connection to Dante primary. The secondary selection represents a physically separate redundant Dante network.

Never assign two adapters connected to the same switch as primary and secondary. Never join primary and secondary switches together. Redundancy depends on isolation between the two failure domains.

The Dante redundant versus switched mode guide explains the endpoint side of this boundary.

Choose interfaces for common scenarios

Primary-only show network

Connect the wired adapter to the Dante switch, select it as primary, and leave secondary unassigned. Confirm the computer address follows the same approved DHCP, static, or link-local scheme as the endpoints.

Wi-Fi may remain available for internet access, but it should not be selected as the Dante primary merely because it has the default route.

Redundant network with two NICs

Connect one adapter to primary and a different adapter to secondary. Verify the two networks use distinct address spaces and separate switches. Controller can then retain control of redundant endpoints if the primary path fails.

Test the roles deliberately: record the baseline, remove one approved path, observe visibility and status, restore it, then repeat for the other path within the test window.

Redundant network with one NIC

Use primary for normal operation so Controller can fully manage primary-only and redundant devices. If primary fails and the recovery plan calls for secondary access, move the cable to secondary and change Controller's interface selection.

Do not leave the selection pointing at the disconnected primary adapter. On secondary alone, some primary-only devices and configuration details will remain unavailable.

Dock, adapter, or VPN changes

USB and Thunderbolt adapters can receive new operating-system names after replacement. VPN or virtualization software can add interfaces and routes. After any such change, reopen Controller's interface selector rather than assuming the remembered selection still represents the same hardware path.

Addressing must match the selected role

On a primary network without DHCP, the computer and endpoints commonly self-assign 169.254.x.x link-local addresses. A DHCP network should show addresses from its approved scope. Static addresses must match the intended subnet policy.

For a secondary network without DHCP, follow the current Audinate guidance and the site's documented secondary addressing design. Do not copy primary addresses onto secondary or let both computer NICs occupy the same subnet.

Use the Dante IP addressing guide for address diagnosis and ownership.

Shared interface behavior matters

Dante applications on the same computer may share an understanding of the primary Dante interface. Changing the selected interface in Dante Virtual Soundcard or another participating application can therefore affect Controller's path.

Before a show, open every Dante application in use, confirm the approved adapter, and test audio. Do not change interfaces while recording or carrying program audio without a defined mute, stop, and rollback procedure.

Troubleshoot an empty or partial Network View

Follow this order:

1. confirm the intended adapter has physical link;
2. open Controller's interface selector and verify primary/secondary roles;
3. compare computer and endpoint address schemes;
4. remove ambiguity from duplicate same-subnet NICs;
5. confirm primary and secondary cabling is not crossed or bridged;
6. check VLAN, firewall, VPN, and managed-network scope;
7. restart only the affected application after evidence is captured;
8. verify device identity, routes, clock, and real audio.

The Dante device discovery guide covers endpoint and discovery-layer faults in detail.

Validate with failure tests

An interface selection is not proven by a populated device list alone. Verify:

• the expected device and channel inventory;
• full configuration access where authorized;
• correct primary and secondary status;
• a real subscribed audio path;
• behavior when one approved path is removed;
• recovery after the path returns;
• clean events, clock state, and packet counters;
• the documented rollback on the same laptop and adapters.

Run failure tests during an approved window and protect audible destinations.

Document the computer-side handoff

Record:

• laptop name and responsible owner;
• adapter manufacturer, model, hardware address, and physical port;
• primary or secondary role and connected switch;
• DHCP, static, or link-local scheme;
• Controller and related Dante application versions;
• shared-interface setting and applications affected;
• VPN or virtual adapters that must remain disconnected or unselected;
• tested failover, recovery, spare adapter, and rollback.

Keep credentials outside a public rider. Link these notes from the digital audio network tech rider.

Controller interface checklist

• The physical adapter, cable, switch, and link speed are identified.
• Primary points to the primary Dante network.
• Secondary points to a separate secondary network or is unassigned.
• The two Dante roles use distinct address spaces.
• Duplicate same-subnet computer interfaces are removed.
• VPN, Wi-Fi, docks, and virtual adapters cannot create ambiguity.
• Related Dante applications use the intended shared interface.
• Visibility, configuration access, real audio, failover, and rollback pass.

Common mistakes

Trusting the operating system's default route. Controller uses its Dante interface selection, which may differ.

Choosing Wi-Fi because it has internet. The intended wired show network should be the primary Dante path.

Using one switch for both redundant roles. That removes the physical failure separation redundancy requires.

Putting two laptop NICs in one subnet. Ambiguous host routing and discovery can produce missing or unstable devices.

Replacing a dock without retesting. The remembered adapter identity may no longer match the physical port.

FAQ

Which network interface should Dante Controller use?

For a typical show network, use the wired adapter physically connected to the primary Dante switch. Assign a second, separate wired adapter to secondary only when it connects to the isolated secondary network.

Why is Dante Controller using the wrong adapter?

Controller remembers prior selections, while docks, VPNs, virtual adapters, and operating-system names can change. Reopen the interface selector and verify the adapter by link and IP address.

Can Dante Controller use Wi-Fi?

Controller can support available interfaces in some modes, but production media and control should follow the system's approved design. A wired adapter is the normal choice for a local show network because its physical path and link state are explicit.

How do I connect Dante Controller to a redundant network?

With two NICs, connect one to the primary switch and the other to the physically separate secondary switch, then assign their roles in Controller. With one NIC, use primary normally and follow the documented recable-and-reselect recovery plan.

Why does Dante Controller see no devices?

The selected interface may have no link, the wrong address scheme, or no access to the devices' VLAN, subnet, or managed scope. Verify interface selection before changing routes or endpoint configuration.

Keep the network role with the rider

The correct adapter choice should not live only in one engineer's memory. Record the computer, adapter, role, address scheme, switch, tests, and recovery in Techrider.live, where invited collaborators can edit the same rider, save changes, and inspect history before the next show.