Notizen

Pad für temporäre Notizen, die nach dem Congress schnell ihre Relevanz verlieren: https://pad.c3voc.de/MvRxqlWLQo6ZgSJsXSLIPQ.

DDM not reachable

The DDM is available under the hostname ddm.cch.network on port 8443. This hostname resolved to 10.20.30.31 at 39C3. Our Dante devices were placed in the 10.21.121.0/24 subnet, though. When only connected to the Dante network everything works fine as the default Gateway at 10.21.121.1 will route and resolve correctly. Once you add a second interface for e.g. VOC LAN (remote control, file transfers, etc) the VOC gateway will take precedence and you will not be able to reach the DDM anymore.

To fix, set a static route in your operating system to make sure that connections to the DDM will go through the gateway on the Dante interface:

Windows: Execute in an Administrator Terminal: route add 10.20.30.31 mask 255.255.255.255 10.21.121.1

macOS: Execute in an Terminal: sudo route add -host 10.20.30.31 10.21.121.1 This should be removed on reboot, otherwise: sudo route flush (this however will flush all routes, so you may have to reconnect your WiFi and so on afterwards). Be sure that both network devices are plugged in and active before you set the route. After congress remove this route permanently with sudo route delete 10.20.30.31.

Some Dante subscriptions in DVS just don't work?!

Hold on to your butts:

The CCH seems to separate the Dante devices across multiple L2 domains and then routes between them. If your Dante interface is not the default gateway (as it should be if you need to access the internet as well) it is most likely due to your computer not having a valid route to that Dante device to start the subscription.

Solution: Add a static route for the entire Dante Network. It seems that 10.21.0.0/16 is enough.

Windows: Execute in an Administrator Terminal: route add 10.21.0.0 mask 255.255.0.0 10.21.121.1

MacOS: sudo route add 10.20.30.0/24 10.21.121.1 und sudo route add 10.21.0.0/16 10.21.121.1. After each restart or network adapter change, the route must be set anew.

silence viri monitoring

We let viri monitor some of our audio devices. Sometime you want to mute errors or warnings. Write viri a message in element: viri: silence audio/backuprecorder for XX minutes