Se rendre au contenu

KNX guides

KNX IP explained: interfaces, routers and KNX IP Secure

KNX IP connects a KNX installation to an Ethernet network. It is how ETS programs the system, how visualisation servers and apps talk to the bus, and how large buildings use the IP network as a fast backbone between KNX lines. This guide explains the two KNX IP device types, tunnelling and routing, and what KNX IP Secure adds.

1. What KNX IP is

KNX telegrams normally travel over the green twisted-pair (TP) bus cable. KNXnet/IP is the part of the KNX standard that carries the same telegrams over an IP network. It works in two ways:

  • Tunnelling: a point-to-point connection between one client (for example ETS, a visualisation server or an app gateway) and one KNX IP device. The client reaches the TP line behind that device.
  • Routing: KNX IP routers send telegrams to each other as IP multicast, so several TP lines can be joined over the network without a central device.

2. KNX IP interface or KNX IP router?

  • KNX IP interface: offers tunnelling connections only. It is the access point for ETS and for visualisation on a single line. A small home with one TP line usually needs one interface.
  • KNX IP router: also offers tunnelling, and in addition works as a line coupler or area coupler that uses the IP network as the main line or backbone. Each TP line gets its own router, and the routers exchange telegrams by routing.

Check the number of simultaneous tunnelling connections a device supports. Each ETS session, visualisation server or app gateway that is connected at the same time uses one connection.

3. Network requirements

  • KNXnet/IP uses UDP port 3671. Routing uses the multicast address 224.0.23.12 by default.
  • For routing, the network switches must forward multicast between the KNX IP routers. In managed networks, agree IGMP and VLAN settings with the IT team before commissioning.
  • Give KNX IP devices fixed IP addresses or DHCP reservations, so ETS and the visualisation always find them.
  • The IP backbone is much faster than a TP line. Filter tables in the routers keep unnecessary telegrams off the TP lines.

4. KNX IP Secure

Plain KNXnet/IP traffic is not encrypted, so anyone on the same network can read and send telegrams. KNX IP Secure protects the IP side of the installation:

  • Secure tunnelling: each tunnelling connection is protected by its own password, and the traffic is encrypted and authenticated.
  • Secure routing: routers on the backbone share a backbone key, so only devices of the same project can join.
  • Secure devices are commissioned in ETS with the device certificate (FDSK) printed on the device. Store the project and its keys safely: without them the devices cannot be reprogrammed.
  • KNX Data Secure is the companion standard that protects telegrams end to end on the TP bus. The two can be used together.

5. Remote access

Never open UDP port 3671 to the internet. For remote programming or monitoring, use a VPN into the building network or a dedicated secure remote access device, and use KNX IP Secure on the IP side.

6. How to choose for a project

  • One TP line, ETS and one visualisation: one KNX IP interface, or an IP router if a second line may come later.
  • Several lines or areas: one KNX IP router per line as coupler, with the IP network as backbone. Plan the physical addresses of lines and areas first.
  • Count the clients that connect at the same time (ETS, visualisation, app gateways, BMS) and choose devices with enough tunnelling connections.
  • Use KNX IP Secure devices whenever the KNX network shares IP infrastructure with other users, as in hotels, offices and residential buildings.
  • Remember the bus current of each IP device when you size the KNX power supply of its line.

Related guides

Compare KNX IP devices on KNX MORE

Plan the whole project for free

List your rooms and devices in the free KNX project planner and send the request to the KNX MORE team.

Quick view