KLANG:app | Device Discovery

How are KLANG devices discovered on the network ?

Quickly find and manage KLANG devices on your network using the built-in discovery in KLANG:app.

This guide shows you how KLANG devices communicate, how they identify themselves, and how to troubleshoot visibility issues.

You’ll learn:

• How device discovery works over IP networks and OSC via UDP.
• How KLANG:app and KLANG:kontroller find processors.
• What to do when a device is missing.
• Tips for using fixed IPs vs. DHCP.

Ideal for support, setup, and remote troubleshooting.

1. Make sure the KLANG processor is powered and the display or status LED are lit.
2. Check that a network cable is plugged into the control network port and that the network activity LEDs are blinking.
3. On your computer, deactivate and unplug all network adapters that are not required to connect to your KLANG hardware. If you are connected via ethernet cable, make sure to disable WiFi for now.
4. If you want to connect to a KLANG:kontroller, make sure KLANG:app is in Show or Admin mode (Press and hold CONFIG for 3 seconds).

Check the Quick Start Guide for your KLANG hardware:

• Partly overlapping subnets / not identical subnet mask:
  • Broadcast is not received. No answer. KLANG:app doesn’t see device.
  • Check IPs and Subnet and correct where required.

• Two different subnets that overlap:
  • 2+ network interfaces e.g. with link-local (zeroconf) IP address ranges 169.254.x.y/16
  • Windows PCs configure backup auto-ip although other IP configured
  • WiFi interface might have additional auto-ip
  • WiFi Internet DHCP server 192.168.1.x/24 vs. hardwired 192.168.x.y/16
  • It is up to Operating System to decide on which network interface it sends out the broadcast connect request!

KLANG:app communicates over IP network messages. KLANG:app sends OSC UDP messages to KLANG processors on port 9110 and to other KLANG:apps on port 9111. All KLANG:apps listen on port 9111. If this port can’t be opened because it is already used by another application, it uses the next free port.

The device running KLANG:app has to be in the same network and in the same IP address range as the KLANG hardware. Firstly, check that the network cable is connected properly and the network connectivity and activity LEDs are blinking. Check that the device running KLANG:app has proper ethernet or WLAN connectivity and that it is connected to the same network as the KLANG hardware.

As a second troubleshooting step, make sure to temporarily disable firewalls.

KLANG:vier, :fabrik, :kontroller and :vokal use internally two different IP addresses. One for Dante connectivity and one for control data of the 3D in-ear mixing processor. Depending on the Dante switch configuration for  fabrik: and :vier, the two network ports are internally combined (default) or separated (redundant, switch separate control) or VLANs might be configured on :vokal or :kontroller.

In some cases, MS Windows prevents broadcast messages to be sent to all existing network adapters, so the handshake with KLANG:app cannot be completed successfully.

Workaround: Try to deactivate unused adapters like VMware or VirtualBox virtual adapters.

It might be necessary to check Firewall settings. Workaround: temporarily deactivity your computer’s firewall.

Private & Link-Local Address Ranges

These IP address ranges are reserved for private networking and local communication. They are not routable over the internet and are used for internal LAN configurations. The Link-Local range (169.254.0.0/16) is automatically assigned when a device fails to obtain an IP address via DHCP and is often used for Zeroconf, Bonjour, or APIPA (Automatic Private IP Addressing). This range is defined in RFC 3927. Private address spaces are defined in RFC 1918 and grouped into three size classes — A, B, and C — each suitable for different network scales. A clear understanding of these ranges is essential for secure, isolated and reliable local network setups.

Multicast Range

Multicast IP addresses are used for group communication where one sender transmits data to multiple receivers simultaneously. This method is common in networked audio systems such as Dante.

Subnet Masks

Subnet masks define how IP addresses are grouped and routed within a network. By creating smaller, manageable subnets, you can isolate network segments to improve performance, security, and address efficiency. Think of an IP address like an address format: “country.city.street.house”

Subnet Masks & CIDR Notation

CIDR (Classless Inter-Domain Routing) notation is a compact way to represent IP address ranges and their subnet masks. It appends a slash followed by a number (e.g., /24) to an IP address, indicating how many bits are used for the network portion of the address.

• For example: 192.168.1.0/24 means:
  • The first 24 bits are reserved for the network
  • The last 8 bits are for host addresses
  • This results in 254 usable IP addresses

CIDR makes subnetting more flexible than traditional Class A/B/C networks and is now the standard for IP allocation and routing. It’s used in everything from home routers to large enterprise and cloud network setups.

For further reading and official definitions, see RFC 4632 – Classless Inter-Domain Routing (CIDR) and the Wikipedia article on CIDR.

Common Subnet Masks

More Specific Examples

Broadcast Address

Broadcast IP addresses play a key role in KLANG’s automatic device discovery process. When a device sends a broadcast message, it reaches all devices on the same subnet.

• Send only one message to reach all devices on the subnet.
• The broadcast address is calculated from the device’s own IP address and subnet mask.
• All receivers must have the exact same broadcast address as the sender.
• This requires using the same subnet mask on all devices.
• No mix of 255.255.255.0 and 255.255.0.0 is possible within the same subnet.
• Broadcasts can slow Wi-Fi networks down to their minimum transmission speed.
• Without additional configuration (e.g. IGMP), multicast traffic is handled as broadcast on most networks.

Glossary

• DHCP: Dynamic Host Configuration Protocol automatically assigns IP addresses and subnet masks from a server or router. It is convenient for large or changing networks.
• Link-local, Zero Conf: Also known as Zeroconf or Bonjour, it allows devices to self-assign link-local addresses in 169.254.0.0/16 when no DHCP server is available.
• Static / Fixed IPs: Manually configured IP addresses and subnet masks ensure predictable network routing and are often used in dedicated audio networks.
• Subnet Masks: Define which portion of the IP address belongs to the network and which part identifies the host device. All devices must share the same subnet to communicate directly.
• Gateway: The network router address that forwards traffic to other subnets or to the internet. Usually not required for closed audio networks.
• Unicast: One-to-one communication between two specific IP addresses.
• Broadcast: One-to-all communication within the same subnet (e.g. used for device discovery).
• Multicast: One-to-many communication to subscribed devices only. Used in networked audio systems such as Dante for efficient data distribution.

_{updated pdi 2025-10-07}