The “IF” is because specifics often matter
. Dante has come up a few times in the forum, let me add some details here since I’m pretty familiar with [u]Dante audio networks[/u].
n.b. I wrote more than intended, but easy to explain in one post, once - since there are a lot of “IF” with Dante
Any Mikrotik router or switch would work, with the default config, for Dante – “IF” Dante was only thing on the network and hardware offloading remains enabled for config. Where you can get into trouble is “IF” a network gets saturated with traffic, or it flows through complex firewalls/etc. with processing delays. At event/venue, it’s easy to control that only AV devices are connected to router/switch, so “if” that’s all a 1G switch/router is doing, there is no need for QoS since everything is below line-rate of the switch chip. How to deal with pro-equipment’s management networks (since some have mobile apps/etc) is where some Mikrotik is useful to do NAT/Wi-Fi/etc. to be able to control pro things & often there is a “redundant” Dante network - all kinda different problems than a home/corp/chruch/etc. But the Dante audio just needs basic L2 switching and be fine.
Now in the “home context”, or anyplace where there general internet traffic on the same switch. i.e. NAS, NVR+cameras, VoIP, controls system, or perhaps most problematic would be kids/etc with multi-GB game downloads kinda things… This is where saturating a network is a possibility, since you cannot control what other network users are doing. So some a “real” switch with hardware QoS is needed. Dante device will take care priority tagging when sending packets. And Mikrotik has a document how to setup on something like the CRS to use “priority marks” added by Dante devices to make sure they get priority on the switch:
https://help.mikrotik.com/docs/pages/viewpage.action?pageId=189497483#QualityofService(QoS)-Dante
Only bit of complexity is Dante uses it’s own protocol by default, but supports a newer standard called “AES67”. IMO, AES67 should not be used unless there is some legit need. The most common case for AES67 be using Linux as an audio source. Dante protocol is not support on Linux, but there are third-party AES67 drivers. But using AES67 mode requires setting ALL Dante devices to use AES67 mode. IMO, if “Linux Dante support” was an issue, the hardware AVIO USB dongle, I believe, work to get Dante to Linux & better than CPU-bound software anyway. Changing Dante to AES67 carries some other limitations too.
I mention Dante’s AES67 support, since in context of selecting a Mikrotik switch… “IF” AES67 mode was going to be needed… getting a Mikrotik switch that support PTPv2 clocking be advisable. See “Standard Dante” uses PTPv1 and has some built-in schemes for clocking, so nothing is required from a network switch for the audio clocking. But…AES67 uses PTPv2 for time clocking. While Dante QoS marking are on a lot of the switches (see docs for which ones), PTPv2 support is more limited. So specifically with the CRS354-48G-4S+2Q+RM mentioned does NOT support PTPv2. So while AES67 work without switch support, “IF” buying a new switch, I’d opt for one with PTPv2 support for AES67. Mikrotik lists their PTPv2 switches here: https://help.mikrotik.com/docs/display/ROS/Precision+Time+Protocol
On whether to VLAN or not… that’s a tricker question. If you use QoS setting on a switch, Dante should be fine on some shared LAN. This is often easier, especially since tools like Dante controller require being on the same LAN as Dante audio to control it. But a separate VLAN also work, just to configure Dante you’d have to use the Dante network. And possible there may be related control with Dante devices that need some shared LAN. Kinda depends exactly what Dante things are involved. You’d still want the Dante QoS settings on switch in either case. And all Dante things do have to live on SAME LAN segment, since mDNS discovery used by Dante only works a single Layer2/ethernet/VLAN subnet (same limitation other things that use mDNS on RouterOS).
The switch I’m eyeballing is the CRS354-48G-4S+2Q+RM and the router probably an RB4011 (internet service is fiber 1Gig symmetrical).
If you have the Elon stuff… I’d just go to the RB5009 that’s more modern than RB4011. Although for Dante, it won’t matter since Dante is switched not routed.
Cheetsheet: Dante audio networking
- Dante devices use mDNS to announce the IN / OUT audio interface on a LAN/VLAN
- Devices will try DHCP to get an IP address from a router. But happy to use it own self-assigned 169.254.x.x address if no DHCP Server is available - this works since mDNS still find the devices on 169.254.x.x LAN & means technically no router is needed, just a switch for Dante to work.
- While Dante has Java-based “Controller” that runs on PC to control the mapping between INs and OUTs of all devices, it does NOT need to run as the devices themselves maintain the needed connections to other Dante device. And other Dante-enabled like networked audio mixer can also do channel mapping. The happens via a Dante-specific protocol, again relaying on mDNS and/or multicast to do this (no server, no cloud, no router needed, just L2 for Dante’s multicast+mDNS)
- Dante devices themselves mark DSCP packets for prioritization, so any “smart switches” just need to prioritize those since they should come already priority marked.
- But… to avoid needing prioritization, Dante has “network latency” setting - this “buffers” audio packets so if some switch was “slow” you can just increase the Dante network latency to compensate. Anything below 10ms latency is not perceptible to human ears (some say 20ms, but Dante goes with max 10ms to be safe), so it’s not end of world if using 5ms.
- But at 10ms max…Dante will not run over Wi-Fi – so using any 5Ghz mesh is out-of-the-question. Everything must be connected via ethernet. One side note, 60Ghz links have been known to work to carry Dante, since latency is lower at 60Ghz than 5Ghz.
- Now with different Dante devices support slightly different levels of latency. For example, Dante has “Virtual Soundcard” and “Via” software for Mac/PC that can route PC audio to a Dante network - but the software lowest latency setting is 4ms (since it CPU processing). The AVIO adapters to convert XLR/BT/USB to ethernet+Dante, go to 2ms. While something like a mid-range Yamaha pro mixer can go as low as 0.25ms (see below):

- The above table from a Yamaha shows Dante’s tables of “# of switches” vs “latency” - and how Dante presents networking to non-networking people – so it uses a conservative assumption of packet processing delay in consumer-grade ethernet switch.
- The presentation from Dante’s “Level 3 Advanced Networking” is likely one of the best presentations on IP/OSI model/DNS/multicast/VLAN/subnets/ARP/DSCP/etc. more generally. Most of Dante’s video/docs/etc do an great job of explaining networks, beyond just the Dante audio part.